HI everyone, we released an update earlier this week to the behavior of OTA updates and the Update App screen following some feedback/bug tickets around confusing behavior. More specifically, there was an edge case where a user would only see the update app screen after downloading a new build - which is a pretty poor experience.
Here is now the logic works with the new update:
We check to see if the user’s app is on a supported live version on app load in addition to the existing server side action checks
If a user downloads the app for the first time or updates the app to a new build and there is an OTA on that build version, the OTA will be applied right away. This will result in a slightly longer initial load time (+1s), but ensure that the first experience with a build is never the update app screen
(existing) if a user is already using a build version and an OTA becomes available, the OTA will be downloaded in the background when the app is opened and then applied when it is re-opened. If the build live version was deprecated, the update app screen will be shown and the OTA will be applied the next time the app is re-opened
My advice would be to publish a new build and test from there to ensure that this latest build has the latest code. If you are still seeing the update app screen on that newest build, then that would be an issue.