I’ve run ‘exp publish’ and it appears to complete successful, but the build when loaded not locally is not updated, nor is the updated publish build retrieved from stand alone builds.
Feeling a bit stuck here, does anyone have any ideas? It acts like there is a cache somewhere and that version is what is being delivered instead of the updated version.
I just recently started having the same issue. I was able to work around it by opening the actual desktop expo client and publishing from there. For reference here was the response I was getting when using exp publish, it appeared successful but was not actually updating the app, nor was I getting the text message saying it was published:
MacBook-Air-2:the100 mlapeter$ exp publish
[10:32:28] Publishing to channel 'default'...
[10:32:30] Building iOS bundle
[10:33:20] Building Android bundle
[10:34:07] Analyzing assets
[10:35:04] Uploading assets
[10:35:07] No assets changed, skipped.
[10:35:07] Uploading JavaScript bundles
[10:35:17] Published
[10:35:17] Your URL is
https://exp.host/@mlapeter/the100
I was able to update with the desktop app. I don’t understand why this would be an issue, but as it is for the moment resolved, I’ll revisit when I have more time.
I have the same issue since updating to expo version 29.0.0. When I run exp publish like I always did before my standalone app does not update. When I run my app via the expo app it runs the updated version. There seems to be a problem with the cli
I’m trying to reproduce the issue, and I’m getting the app to reload (suboptimally). Here’s what I’m doing:
Run exp publish for initial version of app
Build standalone for ios in simulator mode (ie) exp ios:build -t simulator
Download binary, run xcrun simctl install booted test.app
Modify app, run exp publish again
Restart app once, but see no changes. Updates says there is a new version available, but new app does not get loaded.
Restart app twice. New changes are successfully loaded in.
The suboptimal part is that it takes 2 restarts to load in the new version of my app, but my changes are getting picked up, which isn’t consistent with what you guys are seeing.
Could someone give a repro or describe what exactly they did to NOT get the app to update at all? Thanks!
As I suspect, your Expo version has to be up to date IN TESTFLIGHT. I just uploaded a new binary to TestFlight and now OTA is working.
So your only option is to downgrade to the Expo version matching your user’s binary in Testflight. Otherwise wait for your Testflight app to be approved
@ericjames That can’t be right, because some of us can update with the XDE but not command line, and I personally haven’t upgraded my expo version since the build was made that’s on the iOS device.
@rbuk i looked into your builds and your published JS bundles, and the problem is that your standalone build supports up to SDK 28 and you’ve been publishing JS bundles using SDK 29.
Your standalone build will only pull in JS bundles it is compatible with. For example, consider a situation where SDK 29 introduces a new module, A, and your new JS bundles uses module A. If your old SDK 28 standalone build were to pull in this incompatible JS bundle, the call to module A will result in an error because the native code just isnt there. This is why we only allow standalone builds to pull in compatible SDK JS bundles.
Yes they are! As I said, it looks like the standalone Testflight version must match the SDK you are publishing, since manifest changes require a new build.