Element which stores the solution typed by the user

that’s not an option I was talking about, though. The setting on Android I mentioned is not used for switching the typing on and off, but instead for switching between two different typing methods (android/html).


I was looking into the code and started wondering if the issue is with the #typeans element itself. This element is not something specific to the card template or Android – it is the general id that Anki assigns to a typing field on both desktop and Android. The fact that it is also mentioned in the manual alongside AnkiMobile makes me think that on iPhone Anki works the same way in this regard.

Could you take some screenshots of how a typing-in card looks on your device? The appearance alone should have meaningful implications, but it also would be helpful to know, how the on-screen keyboard works in this case.


The issue I suspect now is one with a part of JS which is supposed to automatically flip a card to the back after a multiple-choice button is clicked. Unfortunately, in contrast to AnkiDroid the iPhone app does not have a public API for this (and will unlikely have one). Without it, even if the rest of the code is fixed, multiple-choice cards will require manually pressing the “Show Answer” button each time after an answer is selected.