NotebookBloom: “Anki not detected” usually means one of these three things
NotebookBloom: “Anki not detected” usually means one of these three things
I changed my priorities after watching where people actually got stuck.
Push to Anki is local. The browser is trying to reach Anki Desktop through AnkiConnect at 127.0.0.1:8765.
• Keep Anki Desktop open while pushing cards.
• Install AnkiConnect with add-on code 2055492159.
• Restart Anki after installing or updating the add-on.
If the connection still fails, the cards are not necessarily broken. The local bridge is unavailable. Exporting an .apkg file is the simplest fallback because it does not use AnkiConnect.
A failed button should tell the user what to fix, not leave them guessing.
I am curious how other builders decide when onboarding guidance is more valuable than another feature.
