Hey @jesse thanks for the response, If you check your documentation for configuration of the OTA updates here: https://docs.expo.io/versions/latest/guides/offline-support.html you will notice that it says on iOS background updating is experimental and needs to be manually enabled.
This leads me to believe that on iOS the standard behaviour is to block the UI thread and download the new update during the
<AppLoading /> display.
Is there a way to toggle between rather or not an update should be downloaded in the background or have a UI blocking affect? For example, if you’re rolling out a new API and a new version of the application with new features that talk to that API. That would be a “Required” update, as you would want everyone on the same version to make sure that conflicts don’t happen.
I understand that reverse compatability exists for a reason, but that’s not always something that a company will be able to support when bumping a major version.
For most small patches updating in the background is fine, even for some minor feature updates, new features, etc. But in the case of a large update, you want to make sure that the user is forced into it.