ios – Siren library (Drive replace): TestFlight and manufacturing construct will need to have identical variations?

July 15, 2024

1

I’m implementing a Drive Replace function in my iOS software, and I’m utilizing Siren SPM for to fulfil this downside. Is Siren SPM has the limitation, that CFBundleShortVersionString have to be comply with the identical sequence because the AppStore model sequence.

I’ve a sequence of TestFlight model (CFBundleShortVersionString), all the time better than the Appstore model. Model towards every TestFlight construct present in desk under

TestFlight (CFBundleShortVersionString) | AppStore variations

         3.0.5                          |                    1.0.6
         3.0.4                          |
         3.0.3                          |                    1.0.5
         3.0.2                          |                    1.0.4

So, whereas As far I do know Siren SPM all the time examine CFBundleShortVersionString with AppStore model, which is rarely be legitimate in my case.

Questions:

1 – Is Siren SPM (https://github.com/ArtSabintsev/Siren) actually have this limitation? (situation above): if sure

2 – How will I implement this situation?

3 – Many of the options on web compares CFBundleShortVersionString with Appstore model, so what’s the good apply? The one which I’m already applied or the one that’s AppStore model ought to be identical as TestFlight model.

Supply hyperlink