26.05: correct type-in answers marked "Again" - "does not match" every time

Anki 26.05 (e64c6b1a), macOS, Qt 6.11.0, Chromium 140.

Card type: Basic (type in the answer). Since updating to 26.05, every
correct answer triggers:

“Typed in answer does not match. Rated as Again, ignoring the answer
button you pressed.”

Wrong answers behave normally - this only happens when the typed answer
is actually correct. Started immediately after the update; nothing else
changed on my end (note content, field values, template - all unchanged
and verified clean of stray whitespace/HTML/unicode).

Ruled out a timing issue: waiting a full second before pressing Enter
makes no difference.

The message also causes the revealed answer content to disappear from
the screen after it fires.

This looks like it could be related to #4407 (“Fix unescaped HTML in
correct type-in answers”), since that’s the one change in the 26.05
changelog that specifically touches the correct-answer comparison path -
matches the “only fails when correct” signature exactly.

Happy to provide a sample note/field export or debug info if useful.

Anki doesn’t automatically grade your cards based on what answer you type in. And I don’t see that message anywhere in Anki’s code.

  • Do you have an add-on that is auto-grading your cards?
  • Do you see the same behavior when you run Anki in safe mode – Troubleshooting Checklist #2?

That was it, thanks. Found “auto rate typed answer” (addon 1836029849) installed - it has an “on mismatch ignore user rating, always rate as again/1” option that was firing on every review, including correct ones. Confirmed in safe mode the core type-in-answer comparison is fine; the add-on’s own match logic must have gone out of sync with whatever the 26.05 HTML-escaping fix changed on the comparison path.

Disabled the add-on, problem’s gone. Not an Anki core bug - closing this out. Thanks for the quick pointer to safe mode, that’s what nailed it down.

Hopefully you’ll let that add-on dev know that it no longer works.

Done - posted a report in the official add-on thread, post #22.