Hi there - if you updated to a newer SDK version, you’ll need to rebuild and resubmit to Apple and Google, since the old binary currently in the app store doesn’t include the native code for the new SDK version.
If you want to reach users who have the old copy of your app currently in the store, publish your app on the older SDK version.
@ben, okay so OTA updates now works, but still a minor issue, OTA takes affect only after a user closes the app and relauch it. Is ther e a better way ? Or whats the best way to let users know that he/she should close the app and re open it ?
It’s generally a better user experience to wait for users to stop the app before launching the new version. If the user is in the middle of using the app, it’d be disruptive to suddenly launch the update. And if the user backgrounds the app temporarily to use another app, it’d be disruptive to wipe out their in-memory application state.
On Android there’s an experimental API (it may be more likely to be removed or changed – use at your own risk) called Expo.Util.addNewVersionListenerExperimental. When the user launches your app on Android, it will look for updates in the background and then call this listener if it finds updates. This would let you show the user a message asking if they’d like to reload the app.