Expo server crashes often.

[EltonZhong]

ECONNRESET

I served the app with the command: expo start
But it keeps crashing again and again. And I can not get any information from the message.

[tcdavis]

Stack traces that start with ABIXX and ABIYY are very often bad state being cached by the bundler.
Try deleting everything in node_modules and reinstalling, calling watchman watch-del-all, and running with expo start --clear

[EltonZhong]

Stack traces that start with ABIXX and ABIYY are very often bad state being cached by the bundler.
Try deleting everything in node_modules and reinstalling, calling watchman watch-del-all, and running with expo start --clear

OK I'll try, thanks

[EltonZhong]

Stack traces that start with ABIXX and ABIYY are very often bad state being cached by the bundler.
Try deleting everything in node_modules and reinstalling, calling watchman watch-del-all, and running with expo start --clear

OK I'll try, thanks

Not working, expo still crash sometimes, given the only message:

[cklinx]

Same here.

[brentvatne]

what operating system are you folks using? please notice that there is an issue template that you need to follow in order for us to understand the context surrounding your issue. i attached it here again for you to fill it out. we can't help until you do it.

# READ THIS FIRST, PLEASE!

Hello! Thanks for reporting an issue. Please make sure you're posting this in the right place:

1. If this is an issue with Expo CLI, our command line tool, please post it in the
  https://github.com/expo/expo-cli repo instead.
2. If this is a feature request, please vote or post it at https://expo.canny.io instead.
3. If you are unable to create a reproducible Snack example that demonstrates the bug/issue,
  please first post in our forums at https://forums.expo.io/ before opening an issue here!
  (Unless the bug/issue pertains to a standalone, non-ejected build)

Thanks for helping us make Expo better!



### Environment

<!-- In your terminal run `expo diagnostics` and paste the output here. -->

<!-- Please also let us know about your app's target (iOS, Android, Client, Standalone, ExpoKit) -->

### Steps to Reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
  Be specific! If the bug cannot be reproduced, your issue may be closed.
-->

(Write your steps here:)

1.
2.
3.

### Expected Behavior

<!--
  How did you expect your project to behave?
  It’s fine if you’re not sure your understanding is correct.
  Just write down what you thought would happen.
-->

(Write what you thought would happen.)

### Actual Behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Describe this section in detail, and attach screenshots if possible.
  Don't just say "it doesn't work"!
-->

(Write what happened. Add screenshots!)

### Reproducible Demo

<!--
  Please share a project that reproduces the issue.
  There are two ways to do it:

    * Create a new app using https://snack.expo.io/ and try to reproduce the issue in it.
      This is useful if you roughly know where the problem is, or can’t share the real code.

    * Or, copy your app and remove things until you’re left with the minimal reproducible demo.
      This is useful for finding the root cause. You may then optionally create a Snack.

  This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
  Once you’re done, copy and paste the link to the Snack or a public GitHub repository below:
-->

(Paste the link to an example project and exact instructions to reproduce the issue.)

<!--
  What happens if you skip this step?

  Someone will read your bug report, and maybe will be able to help you,
  but it’s unlikely that it will get much attention from the team. Eventually,
  the issue will likely get closed in favor of issues that have reproducible demos.

  Please remember that:

    * Issues without reproducible demos have a very low priority.
    * The person fixing the bug would have to do that anyway. Please be respectful of their time.
    * You might figure out the issues yourself as you work on extracting it.

  Thanks for helping us help you!
-->

[EltonZhong]

Environment

Expo CLI 2.6.14 environment info:
System:
OS: Linux 3.10 CentOS Linux 7 (Core)
Shell: 4.2.46 - /bin/bash
Binaries:
Node: 11.6.0 - ~/.nvm/versions/node/v11.6.0/bin/node
npm: 6.5.0-next.0 - ~/.nvm/versions/node/v11.6.0/bin/npm
npmPackages:
expo: ^31.0.2 => 31.0.6
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1
npmGlobalPackages:
expo-cli: 2.6.14

Steps to Reproduce

1. In my server, run expo start
2. Open the app in ios simulators, ios real device, Android devices, with development mode.
3. Accidentally, the error occurs, and devices cannot load js bundle from expo server.

Expected Behavior

The expo server should serve js bundle stably

Actual Behavior

expo crashes sometimes, given the only message:

When I restart it, everything goes well then, and it still crashes after some time.
Haven't got a clue.

Reproducible Demo

If you really need a demo project, please leave comments.

Thank you.

[pwfcurry]

I've had this issue before, consistently -- I think it might have been something to do with watchman. I restarted my laptop and it went away...

[EltonZhong]

I've had this issue before, consistently -- I think it might have been something to do with watchman. I restarted my laptop and it went away...

While, even if I change to prod mode, it still crashes,

Actually what I'm doing is to make expo server serve my app stable, for continuous integration use. It's a shame that if expo-server is only for development use :(

[EltonZhong]

Hi, @brentvatne, I got something new!

I modified node_modules/react-native/local-cli/cli.js,
added code below:

and it gives the message above, will it help?

[EltonZhong]

[17:44:54] We noticed your tunnel is having issues. This may be due to intermittent problems with our tunnel provider. If you have trouble connecting to your app, try to Restart the project, or switch Host to LAN.
[11:14:02] We noticed your tunnel is having issues. This may be due to intermittent problems with our tunnel provider. If you have trouble connecting to your app, try to Restart the project, or switch Host to LAN.
[14:44:21] We noticed your tunnel is having issues. This may be due to intermittent problems with our tunnel provider. If you have trouble connecting to your app, try to Restart the project, or switch Host to LAN.
[17:05:07] Tue, 29 Jan 2019 09:05:07 GMT uncaughtException: read ECONNRESET
[17:05:07] Error: read ECONNRESET
[17:05:07]     at TCP.onStreamRead (internal/stream_base_commons.js:162:27)
/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/logs/PackagerLogsStream.js:436
    if (chunk.msg.match(/Looking for JS files in/)) {
                  ^

TypeError: chunk.msg.match is not a function
    at PackagerLogsStream._formatMsg (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/logs/PackagerLogsStream.js:436:19)
    at Object.write (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/logs/PackagerLogsStream.js:177:24)
    at Logger._emit (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/@expo/bunyan/lib/bunyan.js:928:22)
    at Logger.info (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/@expo/bunyan/lib/bunyan.js:1053:24)
    at Object.logInfo (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/project/ProjectUtils.js:337:27)
    at _logPackagerOutput (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/Project.js:2275:45)
    at Stream.<anonymous> (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/xdl/build/Project.js:1359:9)
    at Stream.emit (events.js:188:13)
    at drain (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/through/index.js:36:16)
    at Stream.stream.queue.stream.push (/root/.nvm/versions/node/v11.6.0/lib/node_modules/expo-cli/node_modules/through/index.js:45:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start: `expo start --clear`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-01-29T09_05_08_196Z-debug.log
There is a new version of expo-cli available (2.7.0).
You are currently using expo-cli 2.6.14
Run `npm install -g expo-cli` to get the latest version

[TrentonAdams]

I erroneously posted this on react-native, but I'm posting it here now...

Environment

$ react-native info

  React Native Environment Info:
    System:
      OS: Linux 4.15 Linux Mint 18.2 (Sonya)
      CPU: (4) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
      Memory: 889.13 MB / 15.66 GB
      Shell: 4.3.48 - /bin/bash
    Binaries:
      Node: 11.8.0 - ~/.nvm/versions/node/v11.8.0/bin/node
      Yarn: 1.13.0 - ~/.nvm/versions/node/v11.8.0/bin/yarn
      npm: 6.5.0 - ~/.nvm/versions/node/v11.8.0/bin/npm
    npmPackages:
      react: 16.5.0 => 16.5.0 
      react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1 

Description

This consistently happens when the phone is locked or you close the app on the phone. On my machine this takes 3 minutes on the nose. So, I'm guessing there's a 180s timeout on the socket. The problem is, it never recovers when I start the phone app back up again, which causes lost productivity because I have to restart expo, and then wait about a minute for the javascript build. I have a very small project, I can't imagine how painful this would be with larger projects.

[21:39:36] events.js:173
[21:39:36]       throw er; // Unhandled 'error' event
[21:39:36]       ^
[21:39:36] 
[21:39:36] Error: read ECONNRESET
[21:39:36]     at TCP.onStreamRead (internal/stream_base_commons.js:162:27)
[21:39:36] Emitted 'error' event at:
[21:39:36]     at emitErrorNT (internal/streams/destroy.js:82:8)
[21:39:36]     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
[21:39:36]     at processTicksAndRejections (internal/process/next_tick.js:76:17)

Reproducible Demo

This happens with any application, no real need for a demo; it's an expo issue for not being able to recover from a connection reset.

[TrentonAdams]

Oh, one more thing. This will only occur if you actually start the app using the expo app and trigger a javascript build on the expo server. After that I'm guessing it keeps a connection open between the server and the app on the phone to monitor for changes, and that is where the issue lies.

[ghost]

The error disappears once I switch expo to production mode

[iranmarcius]

Same here. But production mode didn't solve it.

[AppleMango23]

need help, facing same problem here too.........

[UchihaVeha]

I have the same problem, server crash every 5-20 min, this really annoying restarting server every 5-20 min

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Maybe the problem because I use the socket.io and websocket in my project? After migrating to expo-cli my websockets connection stop working in development mode

[scottybo]

Happening for me too - was working fine with an Android device connected, but when I connect an iPhone (running ios 10.3.3 on an iPhone 5) I get this error after a few minutes

[cklinx]

Same here, i am using android emulator on win 10/ ubuntu. Any help?

[styrken]

Started to happen after switching to a new laptop 😒 Happens very often.

[ricardovf]

Same here. I deleted the .expo folder and upgraded expo CLI to 2.11.8 but the problem insistis.
OSX Mojave (10.14.2).
Expo (clI) 2.11.8
expo@32.0.6
node v10.15.2
Typescript

[georgeMorales]

Same problem
ubuntu 16.04
expo sdk 32
node v10.15.1
expo cli 2.6.14

[ricardovf]

Same here. I deleted the .expo folder and upgraded expo CLI to 2.11.8 but the problem insistis.
OSX Mojave (10.14.2).
Expo (clI) 2.11.8
expo@32.0.6
node v10.15.2
Typescript

I changed to node v8.9.4 and the problem is gone.

[Deceptio]

Same here:
expo: "^32.0.0"
react": "16.5.0"
react-native": "https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz
node v10.11.0

Environment:
OS: Windows 10
Node: 10.11.0
Yarn: 1.10.1
npm: 6.9.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version 3.3.0.0 AI-182.5107.16.33.5314842

Packages: (wanted => installed)
expo: ^32.0.0 => 32.0.6
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1

Diagnostics report:
/[16:00:27] Request failed with status code 500

[liudmyla-schastlyvets]

The same problem:
Expo CLI 2.14.0 environment info:
System:
OS: macOS High Sierra 10.13.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.0 - ~/.nvm/versions/node/v10.15.0/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.7.0 - ~/.nvm/versions/node/v10.15.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.0 AI-171.4443003
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
expo: ^32.0.0 => 32.0.1
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^2.16.0 => 2.18.3
npmGlobalPackages:
expo-cli: 2.14.0

[AleksandrDorofeev]

Same problem...

Expo CLI 2.14.0 environment info:
System:
OS: Linux 4.15 Ubuntu 18.04 LTS (Bionic Beaver)
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 10.11.0 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
npmPackages:
@types/expo: ^32.0.3 => 32.0.10
@types/react-navigation: ^3.0.3 => 3.0.6
expo: ^32.0.0 => 32.0.6
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^3.3.0 => 3.6.1
npmGlobalPackages:
expo-cli: 2.14.0

events.js:167
throw er; // Unhandled 'error' event
^

Error: connect ECONNREFUSED 127.0.0.1:43725
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)

[tozenda]

Hey there!

Same problem for me. Expo server crashes without apparent reasons.

Environment

Expo CLI 2.14.0 environment info:
System:
OS: macOS 10.14.4
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.6.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
IDEs:
Xcode: 10.2/10E125 - /usr/bin/xcodebuild
npmPackages:
expo: ^32.0.0 => 32.0.6
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^3.8.1 => 3.8.1
npmGlobalPackages:
expo-cli: 2.14.0

Error is :

events.js:173
throw er; // Unhandled 'error' event
^

Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:162:27)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process.internalTickCallback (internal/process/next_tick.js:72:19)

[mohameddroussi]

I am having the same issue.. anyone have any insight on this?
`events.js:174
throw er; // Unhandled 'error' event
^

Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)`

[ImBeCiliC]

Someone tried to downgrade their node to version 8.16.0? Some reported that this solves the crashing expo-cli.

[azadious]

I have downgraded node to version 8 from version 12. Now I have not encountered this problem at all.

[SamDe4574]

I have the same issue, I have to restart Expo, everytime this happens, any fix for this issue?

[jemgold]

Getting this a bunch

  Expo CLI 3.7.1 environment info:
    System:
      OS: macOS High Sierra 10.13.6
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.10.0 - /usr/local/bin/node
      Yarn: 1.13.0 - /usr/local/bin/yarn
      npm: 6.10.3 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 1.5 AI-141.2422023
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      @types/react: ^16.8.23 => 16.9.2 
      @types/react-native: ^0.57.65 => 0.57.65 
      @xstate/react: ^0.8.1 => 0.8.1 
      expo: ^35.0.0 => 35.0.1 
      react: 16.8.3 => 16.8.3 
      react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8 
      react-navigation: ^3.12.1 => 3.13.0 
    npmGlobalPackages:
      expo-cli: 3.7.1

[WoutVanneste]

Working on a project and I get this error a lot of times.

If I don't do anything on the app, it doesn't happen all the time, or it takes a lot of time before the error occurs.
If I actually do something on the app (in my example, signing up a user to my firebase), the error pops up a few moments later.

EDIT: Sometimes, the error doesn't pop up at all, but it's working or not working at random now.

Some more information about my environment:

Any ways to work around this error?

[stickyburn]

Hey guys, randomly started facing the same issue recently. I was wondering if this is an OS specific issue? I am viewing expo on my android app.

[rgoulter]

This isn't an OS specific issue.

It seems it's just a case of one of the servers not graciously handling a socket error. (In Node v8, socket errors had a default error handler; since Node v10, they don't).
Easiest way to run into this error (as is pointed out upthread) is to just close/lock your phone, and wait for a few minutes.

[Jordhan-Carvalho]

The error appears to occur only if you are using a real mobile device.

[JimVanEeden]

The error appears to occur only if you are using a real mobile device.

This is definitely not the case for me, both with IOS and Android simulators I experience this problem.

[stickyburn]

Okay so just upgrading my expo cli somehow helped... I understand this is a socket issue but npm -g install expo did the magic somehow. A temp fix I can think of is using your Android phone on caffeine mode or just put the screen to never sleep.

[Nantris]

@yashank09 there's been many times I thought it helped, just to find it did not. Are you really sure it helped? If so, what version did you start on and what version is working better for you?

[SPineapple]

I am having the same issue when I ' expo login ' I cannot login in my Terminal even though I can sign-in in Expo website .

read ECONNRESET
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)

And I need to login because of expo notification feature, please help.

[Nantris]

@SPineapple I think that's a distinct/different issue. You might want to see if there's another thread of that specifically, or if there's not, open a new issue. Make sure that your firewall isn't blocking the request first though.

[arnaud-cortisse]

I used to encounter this issue a lot.
Lately I've been using an Android phone instead of an emulator and I've never encountered it again...

[Nantris]

@arnaud-cortisse Weird. I had this issue exclusively with a physical phone.

[angel-luis]

Well, I've noted that it only happens with my Xiaomi phone. With the iPod Touch works fine.

[kevgrig]

Great news, this issue is fixed for me with expo-cli 3.11.2 based on PR #1368. I upgraded expo-cli and then started with expo start -c.

It seems what was happening was that log messages would get split into chunks and if a chunk happened to be a string with an integer, it would get coerced into an integer and the match method wouldn't exist. The fix was to skip the match check if the chunk isn't a string. This happened to me consistently because I had log statements that would dump large, prettified JSONs which included lots of integers with whitespace around them. I suspect the randomness of this issue for some people depended on various factors of chunk size, debug log contents, application behavior, etc.

[natecartwright]

Still get this error on expo-cli 3.11.3, after an idle period or device "sleep":

INFO
16:17
Starting Metro Bundler on port 19001.
INFO
16:17
Tunnel ready.
INFO
16:17
Building JavaScript bundle: finished in 410ms.
ERROR
16:21
events.js:186
throw
ERROR
16:21
er; // Unhandled 'error' event
^

Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:183:27)
Emitted 'error' event on Socket instance at:
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:77:11) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'
}

[kevgrig]

@natecartwright Did you do expo start with the clean (-c) option? Also, the ECONNRESET is one of the symptoms of the problem but could also be a symptom of a different problem; do you have any other error stacks anywhere related to TypeError: chunk.msg.match is not a function or a different error?

[vmaark]

I have the same error all the time. Using ios simulator, expo version 3.11.1. I'll try for some time with the -c option.

events.js:180
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:183:27)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 'ECONNRESET',
  code: 'ECONNRESET',
  syscall: 'read'

UPDATE: using -c does not help

[kevgrig]

@vujevits One cause of this problem was fixed in 3.11.2 so please upgrade and try again.

[vmaark]

thanks @kevgrig , upgrading solved the issue.

[katontech]

I have the same problem during expo start very often.
Also, there is no difference with expo start --clear.
I started using expo-cli 3.11.3 and at the time this problem did not occur, but it does in the latest version.
My current environment is as follows.

Expo CLI 3.16.1 environment info:
System:
OS: Windows 10 10.0.18363
Binaries:
Node: 12.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Users\masa\AppData\Roaming\npm\yarn.CMD
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.6.0.0 AI-192.7142.36.36.6241897
npmPackages:
expo: ~36.0.0 => 36.0.2
react: ~16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4

[EvanBacon]

Currently it's fixed in the latest, if someone has this problem again please feel free to open a new issue.