ankidroid
[New study screen] Card was modified error when tapping the answer buttons quickly
Checked for duplicates?
- [x] This issue is not a duplicate
Does it also happen in the desktop version?
- [x] This bug does not occur in the latest version of Anki Desktop
What are the steps to reproduce this bug?
- Open the new study screen with a few cards to review.
- Spam the answer buttons or gestures.
Expected behaviour
No error.
Debug info
AnkiDroid Version = 2.23.0alpha8 (f9e524a31c98e4f5d922f7b2c5217efe4d350009)
Backend Version = 0.1.62-anki25.09.2 (25.09.2 3890e12c9e48c028c3f12aa58cb64bd9f8895e30)
Android Version = 13 (SDK 33)
ProductFlavor = full
Device Info = Xiaomi | POCO | mondrian | mondrian_global | 23013PC75G | qcom
Webview User Agent = Mozilla/5.0 (Linux; Android 13; 23013PC75G Build/TKQ1.220905.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/142.0.7444.106 Mobile Safari/537.36
ACRA UUID = 4afc3b3f-e93f-4a66-bc71-2b9476ef9eb0
FSRS = 5.1.0 (Enabled: true)
Crash Reports Enabled = true
(Optional) Anything else you want to share?
I don't remember this happening before. However, I have got this and similar errors in other ways; see https://github.com/ankidroid/Anki-Android/issues/17933#issuecomment-3320359500.
Huh, this's weird; I thought you scrapped the ripple effect for answer buttons PR (#19085):
https://github.com/user-attachments/assets/07b53c33-ee66-4c6d-ba2c-d64960ed6264
Research
- [x] I have checked the manual and the FAQ and could not find a solution to my issue
- [x] (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)
I've known about this for a long time. It's easier to reproduce it by tapping the answer button and the screen with a gesture assigned to an answer at the same time (or to an action like delete).
The issue is basically sending an "answer request" before another one was processed in the same card. Part of the consequences of doing stuff asynchronously
Will fix it when I find a solution that I like enough.
Interestingly, I can't reproduce this in v2.23.0beta3.
Details
Also, there is no ripple effect unlike v2.23.0alpha8 (and, I have to say, it feels good without it).
https://github.com/user-attachments/assets/4d8838ae-de6d-4011-8a50-82946bc3c18d
I even tried with Brayan's method (tapping with two fingers) and it just does both actions (reveals the answer then answers, or answers then reveals the answer if it's already revealed):
https://github.com/user-attachments/assets/27465864-55c3-4c24-b8b9-62b4da381332
For completeness, here's a recording of the bug in v2.23.0alpha8
https://github.com/user-attachments/assets/b9f9a09b-bbef-4da0-9e1b-a95dde4f2fdb