The Android app is full of game deciding bugs. The two most annoying are:
- You make a move, the opponents clock is counting down, he doesn't move for a long time, you try to go the main page and back to the game, suddenly one of several bad things have happened: the opponent clock is not as far run down as when you went to the main screen, instead the opponent made a move but the app failed to show you and to show you that your time is now running. Sometimes the opponent has even claimed victory on account of you having left the game(!).
Sometime something similar to this happens even in the beginning of the game but where you can't move even if it's your turn. Or your clock is running down even after you make your move.
- happens mostly on fast games with fast moves and premoves. You tap a piece, the magnify animation stops mid animation, the piece seems to be selected but isn't. You can only fix by tapping another one of your pieces. If you have a king, nothing to do, clock will run out.
All of these bugs seem to be parallelism/concurrency/threading bugs.
The Android app is full of game deciding bugs. The two most annoying are:
1) You make a move, the opponents clock is counting down, he doesn't move for a long time, you try to go the main page and back to the game, suddenly one of several bad things have happened: the opponent clock is not as far run down as when you went to the main screen, instead the opponent made a move but the app failed to show you and to show you that your time is now running. Sometimes the opponent has even claimed victory on account of you having left the game(!).
Sometime something similar to this happens even in the beginning of the game but where you can't move even if it's your turn. Or your clock is running down even after you make your move.
2) happens mostly on fast games with fast moves and premoves. You tap a piece, the magnify animation stops mid animation, the piece seems to be selected but isn't. You can only fix by tapping another one of your pieces. If you have a king, nothing to do, clock will run out.
All of these bugs seem to be parallelism/concurrency/threading bugs.