OTA Updates without force quit

Is it possible for users to see OTA updates without having to force quit the app? We publish pretty regularly and our users are in their app for extended periods of time. It’s annoying to ask them to reopen the app every time we push a change. Has anyone managed to get around this issue? Maybe set some sort of local flag that says “If app focus, check for new version”

Hey @christate,

You can check for updates in the background, prompt the user if there is one and then restart the app if they choose to do so. An example of this can be seen here: https://docs.expo.io/versions/v31.0.0/guides/configuring-ota-updates#manual-updates



Heads-up that we’ve experienced issues with images that are secured behind a login after reloading on Android (https://github.com/expo/expo/issues/370) (this still happens as of SDK 31). Basically, if you have a cookie set with a SET-COOKIE response header or if you manually pass a header in the source of an Image component, those headers will not be present in the corresponding Image HTTP request post-reload. You could pass a session token/ JWT via URL as a workaround. It’s really easy to miss this during testing because cached images will still show up OK. l If you find some other way around this while you’re implementing reload-on-update (or if you see different behavior entirely), please do let us know!

1 Like

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