To start off, we are really happy with Expo and the way it simplifies app development for our clients.
However we do hit some issue quite regularly; Builds timing out on 504s when trying to connect to the Expo build service.
I found another post that describes almost exactly what we are experiencing: 504 error when checking for build in progress - #4 by suitupalex
We are a happy paying customer of the Expo service, however whilst now having 3 apps in development those errors are beginning to bottleneck our workflow.
Is there anything planned to prevent these issues / improve the load handling of your awesome service?
Regards,
Adrian
Example of what goes wrong, it can also happen later when it shows the build progress:
+ expo build:android --release-channel REDACTED --non-interactive --no-publish
- Making sure project is set up correctly...
[11:43:29] Checking if there is a build in progress...
[11:43:30] Looking for releases...
[11:43:30] Using existing release on channel "REDACTED":
publicationId: REDACTED
publishedTime: 2020-05-01T11:43:13.260Z
[11:43:30] Checking if this build already exists...
[11:44:30] Request failed with status code 504
[11:44:30] Error: Request failed with status code 504
at createError (/Users/vagrant/.config/yarn/global/node_modules/axios/lib/core/createError.js:16:15)
at settle (/Users/vagrant/.config/yarn/global/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/Users/vagrant/.config/yarn/global/node_modules/axios/lib/adapters/http.js:237:11)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)