Hi,
We have continuous integration set up with CircleCI that executes expo publish --release-channel <CHANNEL>
I’m non-deterministically getting the following error output:
[18:37:33] Unable to find an existing Expo CLI instance for this directory; starting a new one...
[18:37:35] Starting Metro Bundler on port 19001.
[18:37:40] Publishing to channel 'android-production-8'...
[18:37:43] Building iOS bundle
[18:38:48] Metro Bundler has encountered an error: ENOMEM: not enough memory, write
[18:38:48] › Closing Expo server
[18:38:48] ENOMEM: not enough memory, write
[18:38:48] Failed building JavaScript bundle.
[18:38:48] › Stopping Metro bundler
[18:38:49] Packager URL http://127.0.0.1:19001/node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&platform=ios returned unexpected code 500. Please open your project in the Expo app and see if there are any errors. Also scroll up and make sure there were no errors or warnings when opening your project.
error Command failed with exit code 1.
Unfortunately, since this is executing in a CircleCI environment, and the error is happening non-deterministically, I’m unable to run expo diagnostics to debug.
Is there a good way to estimate the memory usage of expo publish? Has anyone else run into this issue before? Have others been able to solve it by increasing CircleCI’s max memory as described here?