Describe the bug
Websocket client signal disconnected when react-native APP based on RN sdk goes from Android PIP(picture in picture) mode to normal mode after 20 seconds.
From our debugging, it is caused by the ping time out. So our theory is: when APP goes to Android PIP mode, the RN has gone into background mode, and the ping is not working, when RN goes back from PIP mode to normal, it times out then triggers disconnect.
Additional contextsetTimeout and setInterval don't work in the background. Need to figure out workaround to avoid the need for these or work in background.
Describe the bug Websocket client signal disconnected when react-native APP based on RN sdk goes from Android PIP(picture in picture) mode to normal mode after 20 seconds. From our debugging, it is caused by the ping time out. So our theory is: when APP goes to Android PIP mode, the RN has gone into background mode, and the ping is not working, when RN goes back from PIP mode to normal, it times out then triggers disconnect.
Additional context
setTimeout
andsetInterval
don't work in the background. Need to figure out workaround to avoid the need for these or work in background.