we experience a strange behaviour when trying to use exp CLI with bitbucket pipelines. Once in a while our build hangs, always while executing
node ./node_modules/exp/bin/exp.js login -u $EXPO_LOGIN -p $EXPO_PASSWORD
The output we see in Bitbucket console is:
node ./node_modules/exp/bin/exp.js login -u $EXPO_LOGIN -p $EXPO_PASSWORD 3s + node ./node_modules/exp/bin/exp.js login -u $EXPO_LOGIN -p $EXPO_PASSWORD Success. You are now logged in as letsgig.
but the command doesn’t seem to finish and this step lasts forever.
We’re not sure if it’s an issue with exp or bitbucket infrastructure, but maybe you could help us narrow it down. We tried using the docker image (node:9.11-alpine) - which is used in the pipeline - locally and running exp login multiple times - it worked. Any suggestions how to debug it? I went through the login method code and there’s not much which can go wrong.
Tried running diagnostics report but encountered an error:
node ./node_modules/exp/bin/exp.js diagnostics [12:53:43] Generating diagnostics report... [12:53:43] You can join our slack here: https://slack.expo.io/. Environment: OS: Linux 4.14 Node: 9.11.2 Yarn: 1.5.1 npm: 5.6.0 Watchman: Not Found Xcode: N/A Android Studio: Not Found Packages: (wanted => installed) expo: ^28.0.0 => 28.0.0 react: 16.3.1 => 16.3.1 react-native: https://github.com/expo/react-native/archive/sdk-28.0.0.tar.gz => 0.55.4 Diagnostics report: | / -[12:53:45] Request failed with status code 500 [12:53:45] Error: Request failed with status code 500 at createError (/opt/atlassian/pipelines/agent/build/node_modules/xdl/node_modules/axios/lib/core/createError.js:16:15) at settle (/opt/atlassian/pipelines/agent/build/node_modules/xdl/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/opt/atlassian/pipelines/agent/build/node_modules/xdl/node_modules/axios/lib/adapters/http.js:191:11) at IncomingMessage.emit (events.js:185:15) at endReadableNT (_stream_readable.js:1106:12) at process._tickCallback (internal/process/next_tick.js:178:19)