ankitects / ankitects/ankimobile-issues
Crash with magic keyboard
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 4
- Fork
- 0
- Metriche di merge delle PR
- Metriche PR in attesa
Descrizione
From a private [TenderApp report](https://anki.tenderapp.com/discussions/private/38989-ankimobile-crashes-sigabrt-on-ipados-263-when-a-hardware-keyboard-is-attached):
Hi AnkiMobile team,
I recently updated my iPad (iPad13,6) from iPadOS 26.0 to 26.3 and can no longer use AnkiMobile with my Magic Keyboard attached. Clicking on any deck—whether to review, edit, or browse—immediately crashes the app. AnkiMobile works normally without the keyboard connected, but this significantly disrupts my workflow since I rely on keyboard shortcuts to rate cards and to type when creating or editing them. I thought updating to iPadOS 26.4 would maybe resolve the issue but that didn’t happen.
I decided to look into the crash log itself and extracted the relevant information seen below:
(incident ID: 11E8C5D5-DF88-4FE8-8A82-D557BAC3F784, captured 2026-03-24 at 14:27:06 CST):
App version: 25.09 (build 250900.1)
OS: iPhone OS 26.4 (build 23E246)
Exception type: EXC_CRASH (SIGABRT)
Termination: Abort trap: 6, by the anki process itself
The crash is caused by an unhandled NSException thrown from:
[UIKeyCommand setValue:forKey:]
Relevant portion of the exception backtrace is:
+[NSException raise:format:]
-[UIKeyCommand setValue:forKey:]
[3 Anki frames — imageIndex 0, offsets 2949216 / 627128 / 622492]
-[UIViewController _keyboardShortcutMenuLeaves]
-[UIResponder _enumerateKeyboardShortcutsInChainWithOptions:usingBlock:]
-[UIApplication _immediatelyUpdateSerializableKeyCommands]
Anki appears to be using Key-Value Coding (setValue:forKey:) to configure a UIKeyCommand object. On iPadOS 26.3+, this call now raises an NSException rather than silently succeeding, and since the exception is not caught, it propagates through the C++ runtime, resulting in (_objc_terminate → abort).
This crash is reproducible 100% of the time on iPadOS version 26.4 whenever the keyboard is attached and any deck is opened. The exact location of the bugs are the 3 unresolved Anki frames in the backtrace (offsets 2949216, 627128, and 622492 in imageIndex 0) where they have no symbol names, just raw offsets. Please fix this issue so I can get back to studying.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Valutazione
Questa issue non è ancora stata valutata.