Troubleshooting

Nothing pastes after dictating

Nine times out of ten: Accessibility. Wisspa transcribes fine but can't simulate Cmd+V. Open Settings → About — the Accessibility row should say Granted. If not, use the button there to open System Settings and enable Wisspa. Still stuck? Quit Wisspa, run tccutil reset All com.techguider.wisspa, relaunch, and grant fresh.

Text lands in the wrong app (or a settings window jumps forward)

The paste goes to whatever macOS thought was frontmost when you pressed the hotkey. If you'd just clicked a Wisspa window, an older build could misread that — fixed in 0.4.0 (dictating into Wisspa's own fields now uses a direct internal channel). Update, then re-test.

Keychain keeps asking for your password

Every unsigned rebuild is a new app to macOS, so it re-asks. In dev, put keys in .env — Wisspa reads those first. Signed release builds prompt once for Always Allow and then stay quiet.

Hotkey reassignment doesn't register

The Hotkeys tab pauses all global shortcuts during capture so your keys reach the window. If you walked away mid-capture, press Esc (with no modifiers held) to cancel, then click Change again. If a new combo fails because another app owns it, Wisspa keeps the old one and tells you.

Quiet speech gets thrown away

The silence guard decides "nothing was said" from Whisper's own confidence scores, tuned by your mic calibration. If it's eating real dictation: Settings → General → Re-calibrate (two seconds of silence, then say "hello, hello, hello"), and check mic sensitivity — High loosens the thresholds for quiet speakers, Off disables the guard entirely.

Prompt mode "selected text" capture misses

Some apps (Slack, Notion, some browser tabs) take longer than the default wait to put a selection on the clipboard after a synthetic Cmd+C. Reliable for native apps and most editors; flaky for some web targets. Workaround: copy manually (Cmd+C) before pressing the prompt hotkey.

Screenshot actions fail

They need Screen Recording permission — see Permissions. The action declares it, so Wisspa will tell you that's what's missing; grant it in System Settings → Privacy & Security → Screen Recording.

The pill is on the wrong monitor

It anchors to the display your cursor is on in current builds; if it's misplaced, check System Settings → Displays → Arrangement. Click and drag it if you just want it somewhere else.

Something else entirely

Get the evidence first, then report it:

1. Logs: ~/Library/Logs/Wisspa/wisspa.log — the last few dozen lines usually name the culprit. Verbose logging (Settings → General) captures more, with transcripts redacted.
2. Export Diagnostics: Settings → About → Export Diagnostics bundles redacted logs, version, permission state, and hotkey config into one .zip.
3. File it at github.com/TechGuiderBB/wisspa/issues with the zip attached.