I’m having struggles to understand the flow/meaning of certain expo commands when it comes to OTA.
So, let me detail my current release process:
I’m hosting my app in my own hosting service (firebase).
# export the app
expo export --public-url https://awesome-app-native.firebaseapp.com/
# and deploy it to firebase
I build the standalone app IPA locally (first time I did using turtles servers, but now I do locally)
# get the certificates made by expo during the first try
# build it locally
EXPO_IOS_DIST_P12_PASSWORD=23456 turtle build:ios --public-url https://awesome-app-native.firebaseapp.com/ios-index.json --team-id abcdef --dist-p12-path awesome-app_dist.p12 --provisioning-profile-path awesome-app.mobileprovision
Upload the IPA to iOS (testFlight)
# the path for archive.ipa was generated in the previous step.
expo upload:ios --path path/to/archive.ipa
So, in this whole process, my question is: In what moment does the OTA happen?
I never used expo publish as mentioned in the docs, so what am I missing? What’s the difference between build and publish? Can I have OTA updates without using Expo servers?
So, in other words… doing expo export --public-url <URL> + deploy to firebase is enough for an OTA update. The app (on iOS testFlight) will detect the new version, is that correct?
As far as I understand, OTA updates are enabled by default, but it doesn’t seem to be working…
I already did a new export + deploy to firebase and the assets got updated at ios-index.json. The change was simple, just a new line of text. However, the app at testFlight doesn’t show the new text yet. I already refreshed the app and even uninstall/install it again.