Appstore version build number looks correct but installing incorrect/unreleased build number???

Question

Created Mar ’19

Replies 2

Boosts 0

Views 2.6k

Participants 2

We have new 2 builds, 1.1.1 and 1.1.2 in app connect.

We submitted version 1.1.1 for review and it was approved last night however something weird is happening after downloading the app.

The app store says version 1.1.1 is the current version (as expected). Version history looks correct also.. 1.0 -> 1.1 -> 1.1.1

After downloading the app and opening it and checking version number within the app it says 1.1.1 (as expected.

If you then close the app and re-open it and check version again within the app, the app version is now 1.1.2.

We have a critical bug in 1.1.2 which is why we didn't submit it for review (we submitted 1.1.1 instead).

So why is the app magically changing versions after installing it??

We have already verified that it is indeed running 1.1.2. How is 1.1.2 getting installed on the device when we haven't even submitted it for review??

Boost

Answer 1

dataforce OP

Mar ’19

So we just uploaded a new build to app connect, 1.1.3 and have not submitted it for review yet however all iOS devices are getting this new version somehow?

We have tried on multiple iOS devices with different non developer accounts and they are able to get this unreviewed/unreleased build after downloading 1.1.1 from app store, closing it, re-opening it and then it becomes 1.1.3.

Any clue what is happening here? It seems like we can now push unreviewed updates onto the app store...

0

Answer 2

KMT OP

Mar ’19

Is that app set for auto-release to the store, or manual by dev?

0