Have you changed your account or the package name?
Also, please run that command with EXPO_DEBUG=true
@charliecruzan I didnt change my account or the package name.
An unknown error occurred.
MacBook-Air-de-Alex:react-new-app alexmoret$ EXPO_DEBUG=true expo fetch:android:keystore
┌─────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (3.0.10). │
│ You are currently using expo-cli 3.0.9 │
│ Run npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────┘
An unknown error occurred.
Any idea?
MacBook-Air-de-Alex:react-new-app alexmoret$ EXPO_DEBUG=true expo build:android -c
┌─────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (3.0.10). │
│ You are currently using expo-cli 3.0.9 │
│ Run npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────┘
Checking if there is a build in progress…
Request failed with status code 500
Error: Request failed with status code 500
at createError (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/core/createError.js:16:15)
at settle (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/adapters/http.js:237:11)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1129:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
MacBook-Air-de-Alex:react-new-app alexmoret$
Thanks,
Hey @labmoonwalk, we had some outages in the last 24 hrs (see status.expo.io for more detail) that might be related - if so, you may be able to just try again now.
Let us know if that works!
Hi Labmoonwalk,
sorry about that, we were having some issues earlier today: https://status.expo.io. You should be able to build again.
1 Like
Hi @jess. Unfortunately @labmoonwalk has not been able to build for a while. This topic was posted 23 days ago.
1 Like
Hi @wodin @charliecruzan.
As @wodin told, I still facing the same error.
MacBook-Air-de-Alex:react-new-app alexmoret$ EXPO_DEBUG=true expo build:android -c
┌─────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (3.0.10). │
│ You are currently using expo-cli 3.0.9 │
│ Run npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────┘
Checking if there is a build in progress…
Request failed with status code 500
Error: Request failed with status code 500
at createError (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/core/createError.js:16:15)
at settle (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/expo-cli/node_modules/axios/lib/adapters/http.js:237:11)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1129:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
MacBook-Air-de-Alex:react-new-app alexmoret$
Just to clarify. Im facing this error with a specific build update. If we have any other way to uptade this build, there is no problem. I have tried with turtle, but it doesnt work too.
Thanks,
Hi @labmoonwalk, looks like there was an issue with the credentials for that experience build (explains why you also error’d out when running expo fetch:android:keystore)
Could you try building again? It should be fixed
1 Like
When I run expo build:android its look like im building a new app. 
Last login: Thu Aug 22 12:55:44 on ttys000
MacBook-Air-de-Alex:~ alexmoret$ cd react-new-app
MacBook-Air-de-Alex:react-new-app alexmoret$ expo build:android
┌─────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (3.0.10). │
│ You are currently using expo-cli 3.0.9 │
│ Run npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────┘
Checking if there is a build in progress…
? Would you like to upload a keystore or have us generate one for you?
If you don’t know what this means, let us handle it! 
- Let Expo handle the process!
- I want to upload my own keystore!
Answer:
You’ll have to upload your keystore
Sorry @charliecruzan
Im not a developer yet.
How can I identified the keystone and what’s the address format?
No apology needed!
So when you originally built this app, if you followed the Building Standalone Apps guide, you should’ve backed up your keystore (only you would know the location you chose to keep it). If you don’t have this, you’ll need to contact the Google Support Team and ask if they can reset your key.
Unfortunately, if Google’s support can’t help, then without a local copy of your keystore , you will be unable to publish new versions of your app to the Play Store. Your only option would be to generate a new keystore and re-upload your application as a new application.
Thanks for astutely calling this out! Was naively (and hurriedly) trying to nudge folks who might’ve been affected by yesterday’s outage. Really thankful for your helping out here (and elsewhere!)
1 Like
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.