Just wanted to clarify when to run expo publish? Before or after a build? Does eas build automatically publish to the release channel in eas.json if it has not been published already? In some cases I have done a publish, then build, then submit, but when i run the app in testflight it crashes. But if if i re-run publish, the app works again.
Looks like we have to run expo publish after a build based on my testing. Otherwise I am consistently getting an app crashing on load.
Also I am running these commands in CircleCI and expo publish is failing regularly with similar issues as described below in this closed thread:
Hey – we run expo publish on CircleCI and recently have been running into intermittent failures. Anyone else seeing this, and/or have any idea what may be causing this?
We run expo publish --non-interactive --max-workers 1 --release-channel <RELEASE_CHANNEL>.
I saw older posts saying this may be related to outages on Expo’s end, but not seeing anything like that on
Also, we recently upgraded from Expo 36 to 39. Were there significant changes in how expo publish works…
Is there a solution for this as it is breaking my circle builds intermittently.
you have to run expo publish manually to update. eas build embeds your app code and does not publish any updates. if your app crashes before an update there is a bug in your app code.
the other thing you mentioned re: memory errors, that is not an issue with expo, your ci server is running out of memory when publishing.