- each time you run a build, it uses the latest version of expokit
- each version of expokit supports a range of expo versions, from the latest released version (at the time of writing, sdk 25, if you’re ever wondering what this is just go to docs.expo.io and look at the version picker) to perhaps ~7 or so versions behind. the latest supported version at the time of writing is sdk 19.
- months pass, you decide to go back and update your old app to the latest version and rebuild.
- at this point, your previous build on the app store will support only up to the latest version that was released when you last built it. it will not receive any updates for any newer releases.
another way to handle this, in a way that is very explicit, is to use release channels and create a new release channel for every time you run a build. read more about that here: https://docs.expo.io/versions/latest/guides/release-channels.html
Is there a way to let the old app code know that new app has been released and request user to update the app binary via App Store / Play Store?
If I release my app binary now with sdk25 and release a new app with sdk27 few months later, what is the best way to make the sdk25 app binary let user know that newer version of app is available in the App Store/Play Store?
there’s no built in tool for that but you can build that without too much hassle! apple / google probably expose a web api to check for latest app version, then you can just compare that with the one in your app
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.