[Android] Cannot close WebSocket. repeatedly

[Kerumen]

I upgraded my project from 0.28 to 0.30 and since I have, on Android, this warning message every 2-3 seconds:

Cannot close WebSocket. Unknown WebSocket id 0

With the id increasing.

I did a fresh react-native init and it also appears. So it's not my project related.

[charpeni]

@facebook-github-bot label Android

[charpeni]

cc @frantic

[Kerumen]

I forgot to mention that it appears both on Genymotion and on a real device.

After a bit of debugging it seems to be related to 22fbb6d.

A commit is in the pipe 46417dd but even by cherry-picking it I still have the same problem.

[vonovak]

I also see this.

E unknown:JSPackagerWebSocketClient: Error occurred, shutting down websocket connection: Websocket exception
E unknown:JSPackagerWebSocketClient: java.net.ConnectException: Failed to connect to localhost/127.0.0.1:8081
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.io.RealConnection.connectSocket(RealConnection.java:187)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.io.RealConnection.buildConnection(RealConnection.java:170)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:187)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:123)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:93)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:296)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
E unknown:JSPackagerWebSocketClient:    at okhttp3.RealCall.getResponse(RealCall.java:243)
E unknown:JSPackagerWebSocketClient:    at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
E unknown:JSPackagerWebSocketClient:    at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
E unknown:JSPackagerWebSocketClient:    at okhttp3.RealCall.access$100(RealCall.java:30)
E unknown:JSPackagerWebSocketClient:    at okhttp3.RealCall$AsyncCall.execute(RealCall.java:127)
E unknown:JSPackagerWebSocketClient:    at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
E unknown:JSPackagerWebSocketClient:    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
E unknown:JSPackagerWebSocketClient:    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
E unknown:JSPackagerWebSocketClient:    at java.lang.Thread.run(Thread.java:818)
W unknown:React: Cannot close WebSocket. Unknown WebSocket id 36

[namxam]

Yeah, I can confirm that this is happening for me as well.

[amovah]

I have same problem, using v0.30

[dsimmons]

Seeing the same thing on 0.30, although I can't say for sure that it didn't also occur on 0.29(it's possible that it went unnoticed).

[InnerPeace080]

+1

[qxqxqxqx]

+1,V0.30

[efkan]

+1

[yberstad]

I'm having the same problem, using v0.30.

[thebaconguy]

+1 / v0.30

[troytang]

+1 v0.30

[ignacioola]

+1, v0.30

[lucasyalap]

+1 v0.30

[dotnetprofessional]

+1 I just upgraded from 0.29 which didn't have this issue.

[yonahforst]

+1 v0.30

[aimbot]

I would like to add after upgrading to v0.30 I am seeing this too. When you enable remote debugging the log also spams a lot more.

[druvisc]

I started getting these warning messages after creating and adding some native Android modules.

v0.30

[vladp]

+1. Started seeing it with 0.30 as well (0.29 did not have this).
[update] Upgrading to 0.31 fixed the issue for me

[havaliza]

+1 v0.30

[39otrebla]

+1 v0.30 (w/ custom native packages registered)

[hanemason]

+1 v0.30

[ruihuancao]

+1 v0.30

[WaterEye0o]

+1 v0.30

[varungupta85]

+1 Upgraded from 0.24 to 0.30. It has caused all firebase communication to halt.

[varungupta85]

Upgrading to 0.31.0-rc.1 seems to resolve this error.

[rimzici]

Similar Issue:
RN : 0.42
Happens so often on remote debugging.

`
E/unknown:React: Exception in native call
java.lang.RuntimeException: Cannot send a message. Unknown WebSocket id 2
at com.facebook.react.modules.websocket.WebSocketModule.send(WebSocketModule.java:221)
at java.lang.reflect.Method.invoke(Native Method)
at com.facebook.react.bridge.BaseJavaModule$JavaMethod.invoke(BaseJavaModule.java:345)
at com.facebook.react.cxxbridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:136)
at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
at android.os.Looper.loop(Looper.java:148)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:196)
at java.lang.Thread.run(Thread.java:818)

                                                                       --------- beginning of system

`

[ThaJay]

same issue as @rimzici on RN 42.3

[Hitabis]

@ThaJay @rimzici I'm having the same issue on production. Any updates on this?
Are you guys having this issue only in debug mode?

[GrigoryPtashko]

I've got a similar issue. After a network reconnect I've got this one:

On iOS there is no such error. I've got the app logic to close the websocket after network reconnect and open a new one. On iOS this logic works perfectly. But on Android I've this error. I guess the nature of this error is the same as in the original post. What are we going to do about it?

[ghost]

Same. I get this issue both in debug and production releases on Google Play. I only get this issue on Android.

[guysegal]

+1
We are having A LOT of crashes in production! Is there any progress on this issue?

[ghost]

@guysegal It's the most common crash in production for me as well. They need to fix this ASAP

[joseygordev]

+1

[ghost]

Any updates?

React native 0.51.0

Getting this:

[GrigoryPtashko]

@guysegal @danieldelouya guys, does anyone know how can we draw the RN's team attention to this?

[jiyarong]

+ 1
0.50.3 android

[jiyarong]

before you construct a new WebSocket instance, you need release your prev instance

this.ws.close() && this.ws = null

it works for me

[GrigoryPtashko]

@jiyarong the thing is that this error appears after network reconnect on ws.send(). This happens only on Android. iOS is good. The correct behaviour must be like on iOS: the application must go to websocket onError and there must be graceful websocket recreation. But the Android version just crashes.

[ThaJay]

@jiyarong I have the following code in place:

    try {this.ws.close()} catch (e) {}
    this.ws = undefined

but I can still get the error.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

[LaloHao]

Any update?

[ThaJay]

@LaloHao maybe this one is relevant for you? #3346

[hramos]

It looks like this issue is no longer tracking a particular failure. If you run into a WebSocket error like the above in 0.55 or newer, please open a new issue with more information.