@nick.carroll can you clarify if we deprecate the original build (not OTA) that the users will not see a frozen splash screen or update screen? It is my understanding that for new installs, it will install the original build before applying an OTA update on the next app launch, which technically means if I deprecate the original build, all new app installs will not go past the splash screen or they will see the update_app screen, unless they close and re-open? Starter plans only have 3 live versions now so I need to know my users will not experience a disturbance if I deprecate the original build.
Yes, in short, if you deprecate the original build’s live version, users will see the update app screen on initial download based on the current behavior.
Here is an example to illustrate:
- Build 1.0 is in the app store
- Build 1.0 gets an OTA update
- Build 1.0 being downloaded from the app store does not have the OTA update applied out of the box. Update will be loaded on next app load and applied on subsequent load
- If Build 1.0 live version is deprecated…
- Current behavior
- Update app screen will show after downloading, because live version does not exist. OTA will load in the background. User must restart app to get latest code
- Best Practice: Don’t deprecate latest build live version if an OTA is the latest version. Once an OTA is stable, submit a new build so that new users get the freshest app on initial download
- Current behavior
Note: we are looking into the app loading performance impact of applying an OTA update on initial load, though the guidance would remain the same to minimize app loading times.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.