expo: Unable to build:android because of 500 server error

Hi there,

since yesterdays’s afternoon I’m not able to build my Android standalone application. iOS is working fine, though. I have tried to debug or something, but I cannot find much more information. On Expo web interface I can see the following message:

screen shot 2018-04-30 at 11 47 11 pm

Environment

Environment:
  OS: macOS High Sierra 10.13.3
  Node: 8.11.1
  Yarn: 1.6.0
  npm: 5.6.0
  Watchman: 4.9.0
  Xcode: Xcode 9.2 Build version 9C40b
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  expo: ^26.0.0 => 26.0.0
  react: 16.3.0-alpha.1 => 16.3.0-alpha.1
  react-native: https://github.com/expo/react-native/archive/sdk-26.0.0.tar.gz => 0.54.2

App target: iOS & Android

Steps to Reproduce

build:ios is working fine but build:android has stopped working since yesterday with the following error:

15:45:56 [exp] Making sure project is set up correctly...
15:46:03 [exp] Warning: 'react-native' peer dependency missing. Run `npm ls` in /Users/sergioalvarez/Projects/app to see full warning.
15:46:03 [exp]
15:46:03 [exp] If there is an issue running your project, please run `npm install` in /Users/sergioalvarez/Projects/app and restart.
15:46:03 [exp] Your project looks good!
15:46:03 [exp] Checking if current build exists...

15:46:04 [exp] No currently active or previous builds for this project.
15:46:06 [exp] Request failed with status code 500
15:46:06 [exp] Error: Request failed with status code 500
    at createError (/Users/sergioalvarez/Projects/app/node_modules/exp/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/Users/sergioalvarez/Projects/app/node_modules/exp/node_modules/axios/lib/core/settle.js:18:12)
    at IncomingMessage.handleStreamEnd (/Users/sergioalvarez/Projects/app/node_modules/exp/node_modules/axios/lib/adapters/http.js:191:11)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

We have at least two expo accounts building the same APK (personal and CI).

Any help would be much appreciated, since I can’t debug anything more (or I don’t find any other way to get more information about what’s going wrong)


UPDATE: publish is working fine as well.


UPDATE: ID of a build which has recently failed: 19865bca-a505-4b85-bb81-599bdafe4f75 in case of it helps to clarify anything on the server side.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 39 (12 by maintainers)

Most upvoted comments

It was due to the owner in app.json. The value should be an existing username on Expo platform.

Hi guys. I have a similar error. Can you please help me?

screenshot_5

@sergioalvz after some investigation I found what’s the problem. I’ll try to fix it today and will let you know about the status.

I am getting this issue currently, and have just updated expo-cli, and logged out and back in to expo-cli:

[] ~/{...}/mobile-app <gestures-poc> npm i --global expo-cli
/Users/mattrabe/.nvm/versions/node/v10.9.0/bin/expo -> /Users/mattrabe/.nvm/versions/node/v10.9.0/lib/node_modules/expo-cli/bin/expo.js
/Users/mattrabe/.nvm/versions/node/v10.9.0/bin/expo-cli -> /Users/mattrabe/.nvm/versions/node/v10.9.0/lib/node_modules/expo-cli/bin/expo.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-darwin-ia32@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-darwin-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-darwin-ia32@2.2.8: wanted {"os":"darwin","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-freebsd-ia32@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-freebsd-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-freebsd-ia32@2.2.8: wanted {"os":"freebsd","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-freebsd-x64@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-freebsd-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-freebsd-x64@2.2.8: wanted {"os":"freebsd","arch":"x64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-arm@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-arm@2.2.8: wanted {"os":"linux","arch":"arm"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-arm64@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-arm64@2.2.8: wanted {"os":"linux","arch":"arm64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-ia32@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-ia32@2.2.8: wanted {"os":"linux","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-x64@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-x64@2.2.8: wanted {"os":"linux","arch":"x64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-sunos-x64@2.2.8 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-sunos-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-sunos-x64@2.2.8: wanted {"os":"sunos","arch":"x64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-win32-ia32@2.2.8-beta.1 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-win32-ia32@2.2.8-beta.1: wanted {"os":"win32","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-win32-x64@2.2.8-beta.1 (node_modules/expo-cli/node_modules/@expo/ngrok-bin-win32-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-win32-x64@2.2.8-beta.1: wanted {"os":"win32","arch":"x64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/traveling-fastlane-linux@1.6.2 (node_modules/expo-cli/node_modules/@expo/traveling-fastlane-linux):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/traveling-fastlane-linux@1.6.2: wanted {"os":"win32,linux","arch":"any"} (current: {"os":"darwin","arch":"x64"})

+ expo-cli@2.6.14
updated 1 package in 29.109s
[] ~/{...}/mobile-app <gestures-poc> expo publish --release-channel dev
[09:48:16] Unable to find an existing Expo CLI instance for this directory, starting a new one...
[09:48:19] Starting Metro Bundler on port 19001.
[09:48:21] Tunnel ready.
[09:48:21] Publishing to channel 'dev'...
[09:48:22] Building iOS bundle
[09:48:24] Building Android bundle
[09:48:25] Analyzing assets
[09:48:25] Finished building JavaScript bundle in 2952ms.
[09:48:25] ::ffff:127.0.0.1 - - [16/Jan/2019:19:48:24 +0000] "GET /node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Fmattrabe%2Fwwwroot%2Fbrown-bear-car-wash%2Fworking%2Fmobile-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js&platform=ios HTTP/1.1" 200 4062373 "-" "axios/0.19.0-beta.1"
[09:48:28] Finished building JavaScript bundle in 2439ms.
[09:48:28] ::ffff:127.0.0.1 - - [16/Jan/2019:19:48:25 +0000] "GET /node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Fmattrabe%2Fwwwroot%2Fbrown-bear-car-wash%2Fworking%2Fmobile-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js&platform=android HTTP/1.1" 200 4048826 "-" "axios/0.19.0-beta.1"
[09:48:28] Uploading assets
[09:48:28] Finished building JavaScript bundle in 28ms.
[09:48:28] ::ffff:127.0.0.1 - - [16/Jan/2019:19:48:27 +0000] "GET /node_modules/expo/AppEntry.assets?dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Fmattrabe%2Fwwwroot%2Fbrown-bear-car-wash%2Fworking%2Fmobile-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js&platform=ios HTTP/1.1" 200 - "-" "axios/0.19.0-beta.1"
[09:48:28] Finished building JavaScript bundle in 22ms.
[09:48:28] ::ffff:127.0.0.1 - - [16/Jan/2019:19:48:28 +0000] "GET /node_modules/expo/AppEntry.assets?dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Fmattrabe%2Fwwwroot%2Fbrown-bear-car-wash%2Fworking%2Fmobile-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js&platform=android HTTP/1.1" 200 - "-" "axios/0.19.0-beta.1"
[09:48:29] No assets changed, skipped.
[09:48:29] Processing asset bundle patterns:
[09:48:29] - /Users/mattrabe/.../mobile-app/assets/*
[09:48:29] Uploading JavaScript bundles
[09:48:40] Request failed with status code 500
[09:48:40] Error: Request failed with status code 500
    at createError (/Users/mattrabe/.nvm/versions/node/v10.9.0/lib/node_modules/expo-cli/node_modules/xdl/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/Users/mattrabe/.nvm/versions/node/v10.9.0/lib/node_modules/expo-cli/node_modules/xdl/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/Users/mattrabe/.nvm/versions/node/v10.9.0/lib/node_modules/expo-cli/node_modules/xdl/node_modules/axios/lib/adapters/http.js:236:11)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1085:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

I get the same error when I run expo build:ios.

@brentvatne thanks for the prompt reply working now! i’ve encountered this a couple times now. the status page doesn’t seem to be all that quick to update with these outages. perhaps something to relay. 😃

try run command

expo build:android

@jesse-wang @ClementeSerrano @bermann @javadoffuad I just deployed a fix, so old versions of exp should work now. I’m closing this issue.

Had this issue on exp 55.0.4, upgrading to 56.0.0 fixed for me. npm install -g exp

Hi guys! I’m also having the same issue. I cannot build my app to production

Any clue?

It worked like a charm in both, my personal Expo account and in the CI one. Many thanks! You saved my day 😉