[Bug] The mobile terminal (Android) will go offline when selecting a file for more than 10 seconds

[magicindex]

Log in to the web on the mobile terminal, and the mobile terminal icon will be displayed on the computer. If the mobile terminal clicks on the file to select the file to be transferred for more than 10 seconds, the mobile terminal icon will disappear on the computer. There is no response after clicking the file selected on the mobile terminal, and the mobile terminal will prompt that it is connected again. At this time, the computer terminal icon is normal again. Selecting files on the mobile terminal is normal within 10 seconds.

手机终端web登录，在电脑端显示手机端图标，手机端点击文件进行待传输文件选择时候，如果超过10秒，电脑端显示手机图标就会消失。手机端选中的文件点击后也没有反应，手机端会重新提示已连接，这时候电脑端图标又正常了，在手机端选择文件不超过10秒钟均正常。

[schlagmichdoch]

Please use the provided bug template to create issues in order to make it easier for devs to understand you.

This issue seems to be a duplicate of #247. Please confirm whether this is resolved on the current development branch on this instance: https://dev.pairdrop.net/

[magicindex]

I read #247 and confirmed that the problem is the same. After analysis, I guess it may be caused by the following problem: When a mobile web browser opens a new full-screen page (file selection window), it will pause the previous page to save battery energy and improve CPU, memory, etc. efficiency. When the previous page is restored, the code will reconnect to the network.

After testing: https://dev.pairdrop.net/ The project has solved this problem. Although the peer icon will still disappear, file transfer will still be performed automatically after connecting to the Internet.

我去阅读了#247，确定问题是一致的，经过分析应该猜测可能是如下问题导致：移动端web浏览器当打开一个新全屏页面（文件选择窗口）会把上一个页面暂停，以节省电池能源以及提高cpu、内存等效率。当恢复上一个页面后，代码会重新进行联网。

经过测试：https://dev.pairdrop.net/ 项目已经解决该问题，虽然对端图标依然会消失，但是文件传输依然在联网后自动进行。

[schlagmichdoch]

Alright, thanks for testing! Under some conditions like power saving mode JavaScript on a page is stopped when the OS file selection dialog is opened. The PairDrop server then thinks that the client has left as it does not get a ping after 10s. In the new version the outgoing messages are queued and sent on reconnection which solves this issue. As this is fixed by the new version I’ll close this as soon as it is merged into the master branch.