Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ECONNRESET on phone lock or app closure #23262

Closed
TrentonAdams opened this issue Feb 2, 2019 · 4 comments
Closed

ECONNRESET on phone lock or app closure #23262

TrentonAdams opened this issue Feb 2, 2019 · 4 comments
Labels
Bug Platform: Linux Building on Linux. Resolution: Locked This issue was locked by the bot.

Comments

@TrentonAdams
Copy link

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 300ms 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.

@react-native-bot react-native-bot added the Platform: Linux Building on Linux. label Feb 2, 2019
@hramos
Copy link
Contributor

hramos commented Feb 2, 2019

Is this an issue with Expo, or React Native? If it cannot be reproduced without Expo, I am not sure it belongs in this repository.

@TrentonAdams
Copy link
Author

Oh, I didn't realize they weren't the same project, I'll comment on https://github.com/expo/expo/issues/3227

@AppleMango23
Copy link

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 processTicksAndRejections (internal/process/next_tick.js:76:17)

facing same problem... what can i do? it keep disconnect me with expo and cant reload it anymore...

@hramos
Copy link
Contributor

hramos commented Feb 25, 2019

This issue has been closed. See https://github.com/expo/expo/issues/3227 or open a new issue here if it's unrelated to Expo.

@facebook facebook locked as resolved and limited conversation to collaborators Feb 2, 2020
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Platform: Linux Building on Linux. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants