Closed fractionofadot closed 5 years ago
Re: there is one: [https://github.com/veloce/lichobile/issues/936]
Similar but is a very different behavior than I have described above (but I wouldn't be surprised if it was related).
These are quite different symptoms.
I think that's a serverside issue.
I'm submitting a ... (keep the relevant one):
Bug report
Current behavior: Often, I will be playing a game and waiting for my opponent to move. There is no indication of any network issues: the moving dots do not appear and everything seems normal. But it turns out that the server believes it is my turn to move and the app has not received the message.
An example game: https://lichess.org/0dlO9L3TKLd4
I waited for my opponent to move until their time ran out. I showed as connected with no network problems. In the end, it was I who lost on time, and had no idea.
This has happened more often than I (or anyone except the benefactor) would like ;D
Expected behavior:
If there are any issues with sending or receiving a move from lichess servers, the app should indicate that there is a problem and not behave as if everything is normal. The servers and app should do a check to make sure the app received/sent the latest moves.
Steps to reproduce:
This may be tough to reproduce. It may involve temporarily disconnecting from a network at certain points during, between, or after moving.
Environment information
Pixel 3
Other information: