App is released with phased release (lets call v2.0) and lets say 5% users are using new version of the app. Now there is a critical issue identified and submitted a new version (lets call v2.0.1) again with phased release. Will the initial 5% users cover in the phased release of new version uploaded.
Anyone has how it bahaves?
Best regards.
The 5%'ers need to be configured for auto-update, and are picked at random. They are not notified of their participation/place in line. All users can choose to update manually at any time, meaning they don't need to be in the PR 5% to use the latest version.
See the docs: https://help.apple.com/app-store-connect/#/dev3d65fcee1
If I had a critical release, I'd see if I could request an expedited review while pausing the PR version w/issue(s)....might want to take the app off-sale in all countries as well, so that no new users grab the fouled version.
I have never been through this process but would be keen to understand what would happen in that scenario specifically.
I'm also interested in the update behavior during a phased release. We did a phased release of version 15.0.1. and stopped at 1%. Now we have a 15.0.2 and would like to release this also again staggered, because 15.0.1 still has a critical bug.
What happens in this case with version 15.0.1? Will it be automatically rolled out with the staggered release of 15.0.2? (That would not be our wish). Or will version 15.0.1 then be virtually skipped for the majority of users? (This is what we would hope for).
Does any one know what happens in the case described above?
Hello community,
I was researching to understand the behavior of the described problem as well. Has anybody got a reply or knows a source where to find the answer? Thank you 👋🏼