Troubleshooting

Fixes for the problems people actually hit: a missing microphone, silent call audio, a stuck download, a rejected key, a call that won't finish processing, or a license that won't activate. If nothing here solves it, email support@callmora.app.

Nothing records, or the mic is missing

Recording needs two separate macOS permissions — one for your microphone, one for the call audio itself — and either one missing can leave you with silence.

1. Open System Settings → Privacy & Security → Microphone and confirm Callmora is listed and on. macOS only lists an app here after it has asked, so if Callmora is missing, open its mic picker once (the menu-bar panel, or Settings → General → Audio → Microphone) to trigger the prompt.
2. Open System Settings → Privacy & Security → Screen & System Audio Recording and do the same — the separate permission that lets Callmora capture the call itself, not just your voice.
3. Changed either toggle while Callmora was open? Quit and reopen it — macOS doesn't always apply a permission change to a running app.
4. Still silent? Pick your microphone explicitly rather than leaving it on System default — a disconnected or renamed device falls back silently instead of erroring.

See Recording calls for how the mic and call-audio pickers work day to day.

A local model download is stuck or failed

Local mode downloads its model once, from Settings → Transcription. A slow or dropped connection shows a spinner while Callmora retries on its own; once exhausted, the row becomes a plain error with a Retry button. If the model is present but transcribes badly, or you suspect incomplete files, use Delete and download again next to Model files in the same tab for a clean copy. Details on engines and models are in Transcription.

Transcription or notes fail with a key error

Cloud transcription needs an AssemblyAI key (Settings → Transcription); notes and chat need a separate provider key (Settings → Summary) — OpenAI, Gemini, Claude, AssemblyAI's LLM Gateway, or a custom endpoint. An invalid-API-key banner almost always means the key was pasted with a stray space or got truncated — repaste it from the provider's dashboard.

Key correct but summaries still fail on AssemblyAI's LLM Gateway? Check the plan: AssemblyAI transcribes on its free tier, but Gateway summaries are a paid AssemblyAI tier. Point the summary step at an OpenAI, Gemini, or Claude key instead — see AI notes & chat for the full provider list.

A call is stuck "Processing"

Callmora retries a failed transcript or summary by itself in the background — on reconnect, and again next time you open the app. A failed call shows a Processing failed — the audio is saved. banner with a Retry button, plus a line underneath on the automatic attempt: "Will retry automatically," a countdown, or, once six automatic attempts are spent, "Automatic retries stopped — use Retry." The audio is never deleted while a call waits, so Retry re-runs it from scratch anytime.

License won't activate

The most common refusal isn't a bad key — it's an activation limit: the key is already active on every Mac it allows. Callmora says so directly, naming how many Macs it's on. Open Callmora on one of those Macs and choose Deactivate This Mac in Settings → About, then activate here. No access to the old Mac? Email support@callmora.app with your License ID — shown in your own About tab, or on your Lemon Squeezy order — and the slot can be freed from there. More in Licensing & trial.

Where updates come from

Callmora checks for updates on its own and offers to install a new version when one is available. Check manually with Settings → Updates → Check Now; the same tab shows your current version number.

Reporting a bug

Email support@callmora.app with what you did, what you expected, and what happened instead. Include your macOS version and Callmora's version — Settings → About shows both, plus the License ID if you're licensed, worth quoting for anything account-related.