-
-
Notifications
You must be signed in to change notification settings - Fork 103
Description
Description
Recently, I noticed that an error appeared on write
{“message”:“Broken pipe”,“name”:“Error”,‘stack’:"Error: Broken pipe\n at msgEvtHandler (address at index.android.bundle:1:2669283)\n at call (native)\ n at emit (address at index.android.bundle:1:2598493)\n
This is immediately followed by an error event, which is also difficult to understand
{“message”:“Unhandled error. (undefined)”,“name”:“Error”,‘stack’:"Error: Unhandled error. (undefined)\n at emit (address at index.android.bundle:1:2693977)\ n at anonymous (address at index.android.bundle:1:2661293
In addition, I work with different servers at the same time and have two socket instances, and both servers simultaneously return the same error, and the appearance of the error is unstable. everything can work without problems for a couple of minutes, then both socket instances return an error, go into reconnect mode, after reconnecting the error reappears, a second reconnect is performed, and after that everything starts working normally.
I can't provide an example of the code right now, but if necessary, I can set aside time to prepare an example code.
Steps to reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Or code:
// Your codeCurrent behavior
A clear and concise description of what happened.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant information
| OS | android |
| react-native | 0.76.9 |
| react-native-tcp-socket | 6.3.0 |