I have recently published my app both in IOS and Android. I am using expo. Everything went well. Whenever I made a change in the code I built the app for IOS and Android using expo build:ios/android in order to upload the ipa file to Apple App Store and aab to Google Play Store.
I suddenly realize that, when I publish my currently working code to expo using expo publish (so that I can test code in expo client with others) then I found out that the standalone apps were also updated. I have read the expo publishing update documentation page which makes me somewhat confused. So here I ask the following questions,
- If I publish my code without changing the app.json file should the standalone apps (both ios/android) be updated? Seems yes to me.
- If so, it can be very good (which will save my time by avoiding ios/android review process) but at the same time how can I test code in expo client with others without hampering my production apps?
- The expo publishing update documentation page says, changes to app.json will require re-building the binaries to take effect in the iOS or Android standalone app. Does that also mean that, if I just build using
expo build:ios/android, I don't have to upload those binaries (ipa, aab) to Apple or Google once more? I don't think so. But the documentation is not explicit about it, so I ask this question.
While using expo build, you can use --no-publish flag to prevent publishing your app to the production.
If you would like to build app and not to change code on production, you can alternatively use release channels which will have your app in different environments.
Edited: If you do make minor changes, expo can get the updates by over-the-air (OTA) updates. You can get more information about them by using the link: docs.expo.io/guides/configuring-ota-updates