Selectively forcing OTA updates

#1

We’ve got a detached app and would like to be able to optionally force OTA updates to our app depending on the types of changes/improvements we’ve made. We’d also like to keep the fallbackToCacheTimeout set to 0 for the best user experience, so we’re considering using the Expo Updates listener API to monitor the background OTA update download process and reload if necessary.

Are there any best practices for this? Specifically, we’d like to be able to specify at publish time whether an update should be “required” or not.

One option that comes to mind is to add a custom “forceUpdate” parameter to the app manifest, and have our app updates listener check the parameter after a background download is completed. Any better ideas?

closed #2

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.