Crash/Restart when switching apps while editing any field in Deck Options #20101
Description
Checked for duplicates?
- This issue is not a duplicate
Does it also happen in the desktop version?
- This bug does not occur in the latest version of Anki Desktop
What are the steps to reproduce this bug?
Description
The app fails to restore its state when switching apps while any text input field in "Deck Options" is active. If I am editing a field (like Search, Limits, or Name) and switch to another app, switching back to AnkiDroid causes the dialog to close. If I repeat this action multiple times, AnkiDroid crashes.
Steps to reproduce
Long-press on any Filtered Deck.
Select "Deck Options".
Tap on any input field (e.g., Search, Limit to, or Cards selected by) so the keyboard appears.
Switch to another app (background AnkiDroid).
Switch back to AnkiDroid.
Observation: force open ankidroid again.
After repeat steps 3-5 times i encountered this bug below:
Expected behaviour
The app should seamlessly restore the Deck Options dialog and keep the keyboard open without closing or crashing.
Debug info
Debug Info:
AnkiDroid Version = 2.24.0alpha1-debug (715d151b0e1942b21aa4901775a447998291a982)
Backend Version = 0.1.63-anki25.09.2 (25.09.2 3890e12c9e48c028c3f12aa58cb64bd9f8895e30)
Android Version = 16 (SDK 36)
ProductFlavor = amazon
Device Info = motorola | motorola | monai | monai_g | motorola edge 60 stylus | qcom
Webview User Agent = Mozilla/5.0 (Linux; Android 16; motorola edge 60 stylus Build/W1VB36.62-22-17; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/143.0.7499.147 Mobile Safari/537.36
ACRA UUID = 421499a4-a3a4-4fbb-ae50-330abddb3e07
FSRS = 5.1.0 (Enabled: true)
Crash Reports Enabled = false
(Optional) Anything else you want to share?
Actual behavior
Initially, the dialog closes unexpectedly upon returning to the app. After repeating the process 3-4 times, the app crashes completely and displays the "AnkiDroid Feedback" crash report dialog.
Research
- I have checked the manual and the FAQ and could not find a solution to my issue
- (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)