expo: exp build:android fails

Running exp build:android errors fails. I am experiencing this on both Windows and OS X.

This solution is working as a temporary work around. Expo version is 56.0.0.

$ exp build:android
[11:01:40] Checking if current build exists...

[11:01:41] No currently active or previous builds for this project.
[11:01:42] Publishing to channel 'default'...
[11:01:44] Building iOS bundle
[11:01:45] Error: connect ECONNREFUSED 127.0.0.1:19001
[11:01:45] Set EXPO_DEBUG=true in your env to view the stack trace.

Environment

Environment:
  OS: Windows 10
  Node: 8.11.1
  Yarn: 1.9.4
  npm: 5.6.0
  Watchman: Not Found
  Xcode: N/A
  Android Studio: Not Found

Packages: (wanted => installed)
  expo: ^29.0.0 => 29.0.0
  react: 16.3.1 => 16.3.1
  react-native: https://github.com/expo/react-native/archive/sdk-29.0.0.tar.gz => 0.55.4

Diagnostics report:
  https://exp-xde-diagnostics.s3.amazonaws.com/skempin-e8172ba2-6e87-419c-b5dd-7eb273b98cbf.tar.gz

Steps to Reproduce

Run exp build:android from a fresh terminal.

Expected Behavior

The APK should be built.

Actual Behavior

The build fails.

A temporary solution is to run exp start first and then run exp:build:android.

capture

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 39
Comments: 60 (7 by maintainers)

Most upvoted comments

This works.

exp start
Cancel ctrl c
then do exp build:android.

+340

kevupton on Aug 26, 2018

This is work for me.

expo start
Open another tab
expo build:android

+100

shivnath17 on Apr 29, 2019

This works.

exp start

Cancel ctrl c

then do exp build:android.

I don’t know why but I do the same way with expo-cli and it’s working!

+49

fannyhasbi on Sep 15, 2018

No need to hassle. Just delete .expo folder and expo build:android or expo build:ios, works like a charm.

+28

abduraufsherkulov on Sep 19, 2019

Issue still occurs

+25

Vieshanis on Feb 5, 2019

Probably the bundler didn’t close correctly. So you cannot run another one on the same port. Maybe expo start kills the old process?

+10

julianrod94 on Oct 7, 2018

Can this be reopened? This happens to me on a regular basis, and its frankly just annoying. The workarounds seem to work, but it would be cool to address the underlying issue.

jannikbuschke on May 18, 2020

Another solution is open in a different tab the expo server running yarn start (or npm start) if the project was created under create-react-native-app

cesarodriguez4 on Aug 19, 2018

see this forum comment. https://forums.expo.io/t/error-when-trying-to-run-exp-publish/223/12?u=jorgews.dev

egos-ti on Dec 10, 2019

For me on Windows this worked:

expo start
open a new command tab - expo publish

EdvinasRuo on Oct 11, 2019

This works.

exp start Cancel ctrl c then do exp build:android.

Wao…! it really works…

ZamanGoraya on Sep 19, 2019

Some info: expo start now uses 19002 port but the expo publish and expo build still look for the bundler in 19001. is this related to the latest v33 release?

john20xdoe on Jun 10, 2019

I’m still experiencing the same issue with expo-cli 2.3.5 Upgrading to expo sdk 31 broke our pipeline because the packager is not started automatically anymore.

tonnenpinguin on Nov 8, 2018

the commands recently got changed with the new update exp build:android to expo build:android

Reference: Expo Building Standalone Apps

Nisharunnisaa on Sep 25, 2018

Had the same issue on OSX . Was resolved by:

expo start
once app is running, ctrl c to close the packager.
expo build:android

jimwilde on Jun 3, 2019

Experiencing same issue with expo-cli@2.6.5, solution above helped.

xxdondi on Dec 6, 2018

I am building an android app with expo and encountered this issue as well. Thanks for the solution guys. I just want to share what caused the error. The build requires a Metro Bundler running in port 19001 where this is not running by default as we type in expo build:android and this caused this error

connect ECONNREFUSED 127.0.0.1:19001

so starting the Metro Builder first by typing expo start then start building using a different cmd or tab by typing expo build:android or I haven’t try this yet but share us the result when you does thanks! Add -c to expo build:<platform> example: expo build:android -c

Cheers!

arjorie on Jan 9, 2020

Why is this still an issue?

The workaround with CTRL + C doesn’t help in my case. Luckily, deleting the .expo folder works. Why is it doing an iOS bundle while I want to build Android?

$ expo build:android
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! :)
 false
Publishing to channel 'default'...
Building iOS bundle
connect ECONNREFUSED 127.0.0.1:19001
Set EXPO_DEBUG=true in your env to view the stack trace

rolandoldengarm on Nov 21, 2019

Solved the issue the following way: 1-expo start 2-opening a new terminal window (same project dir) => expo build <platform code>

kalideir on Nov 19, 2019

Thanks ‘expo start’ worked
and then with metro bundler opened I tried ‘expo build:android’

jhonatanyachi on Aug 27, 2019

My build pipeline started throwing this error after I accidentally commited .expo/packager-info.json and settings.json. Removing them from the repository fixed the issue.

jannikbuschke on May 3, 2019

try run command

expo build:android

hendra1 on Dec 20, 2018

Closing since it sounds like this has been resolved in expo-cli

tcdavis on Oct 8, 2018