-
-
Notifications
You must be signed in to change notification settings - Fork 310
Description
What is the problem?
I encountered a weird and pretty severe bug today. After I gave my opponent a takeback (so it was their turn again) my clock was ticking, not theirs!
I made a 12 seconds long screen recording, the file size is quite big, so I apologize for linking it with Streamable! Please refer to the following screen recording:
Let me explain what's happening in the screen recording.
It's my turn after my opponent, black made their move Qxh2. I asked them to take back the move as I wanted to record the bug I noticed. The takeback message appears, I accept the takeback.
Now, pay close attention to the clocks. It is black to move, it's my opponent's turn, their clock is white (active color) but the clock is actually frozen! Take a look at white's clock. My clock is grayed out (passive color) but it's ticking! Mind that after the takeback it's black to move again (my move Re5 was made, it's clearly visible), I can't move again as it's not my turn but my clock is ticking!
Steps to reproduce the bug
- Play a game
- Opponent asks for a takeback
- Accept takeback
- It's the opponent's turn again but their clock is frozen and the user's clock is ticking
App version
0.15.5
Device Info
Xiaomi Redmi Note 10 5G / Android 13 (MIUI 14)
Additional information
In my opinion it's a severe bug because
- Obviously it's a problem that the wrong clock is ticking
- I almost didn't notice it because the active-passive color of the clocks is actually changing but the wrong clock is running and the other is frozen. So it's possible that someone isn't aware that their clock is wrongly running.