How do OTA updates work with Ejected apps?

#1

I’ve read the documentation on here: https://docs.expo.io/versions/latest/guides/configuring-ota-updates

But (like much of the documentation), it’s not clear whether that applies just to “normal” expo apps, or also ejected apps. It keeps using words like “experience”, which sounds like Expo apps you would launch from the Expo client, not Ejected apps which are self-contained.

Anyway, my client claims that they were running version 1.0.22 of my app. That was an over-the-air update. But today they claim that it reverted back to 1.0.13, which was the version of the bundle included in the *.ipa

Is that possible? Or are they likely mistaken and must have re-installed the *.ipa? How does the caching work for OTA updates?

cheers,
-adam

#2

I’ve seen some odd caching behavior as well. What phone was your client on?

#3

hi, there is an issue for this which we’ve deployed a fix for https://github.com/expo/expo/issues/1719

Please let us know if this solves your problem

closed #4

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