This is kind of a hard one to get happen, but on puzzle attempts, if you move too quickly it will count the move as incorrect even when the right move is made. Looks like it may be a race condition.
I believe this mostly happens on multi-move tactics, since I don't normally try to move on the first one until I have a chance to look over the puzzle, so I guess it is possible it could happen on move 1.
That said, it feels like a race condition and the later move gets accepted before the code moves to that and ends up comparing it to the previous correct move.
For example, in a three move puzzle, move 1 and 2 are correct but if move 3 is made too quickly, that move is checked against the answer for move 2; I can't say that is what is happening, but it seems like that may be the case.
I've had it happen on multiple versions and occasions and am pretty confident that I was making the correct moves when it happens.
This is kind of a hard one to get happen, but on puzzle attempts, if you move too quickly it will count the move as incorrect even when the right move is made. Looks like it may be a race condition.
I believe this mostly happens on multi-move tactics, since I don't normally try to move on the first one until I have a chance to look over the puzzle, so I guess it is possible it could happen on move 1.
That said, it feels like a race condition and the later move gets accepted before the code moves to that and ends up comparing it to the previous correct move.
For example, in a three move puzzle, move 1 and 2 are correct but if move 3 is made too quickly, that move is checked against the answer for move 2; I can't say that is what is happening, but it seems like that may be the case.
I've had it happen on multiple versions and occasions and am pretty confident that I was making the correct moves when it happens.
App 4.0.0-21789v4.1.2-21910
Pixel 3
Android 10