Troubleshooting

Start with the three checks

Almost every problem is one of three failures, and thirty seconds of looking tells you which. Hold your dictation key over any text field and watch.

• Does the mic pill appear? If not, the shortcut is not reaching VoiceSnap Pro — a permission or a conflict.
• Does the level meter move while you speak? If not, the microphone is the problem, not the app.
• Does the pill name the app you are looking at? If not, focus is the problem.

Nothing is typed at all

If the pill appeared and the meter moved, the audio was fine and the insertion failed. On macOS, that is Accessibility: System Settings → Privacy & Security → Accessibility, with VoiceSnap Pro switched on, then quit and reopen VoiceSnap Pro. A tick that is already there but not working is the case for removing the entry with the minus button and adding it again.

If nothing happens anywhere on macOS and Accessibility is definitely granted, an app has probably left Secure Input switched on after a password prompt. Locking and unlocking the screen clears it; if it comes back, quit the apps you had open when it started — a browser with a stuck password field and some VPN clients are the usual culprits.

On Windows, check whether the target window is running as administrator. A non-elevated app cannot send input to an elevated one; run VoiceSnap Pro as administrator to dictate into it.

• No mic pill at all: grant Input Monitoring on macOS, or check that your shortcut is not claimed by another app.
• Pill appears, no meter movement: wrong input device, muted input, or Microphone permission not granted.
• Pill and meter fine, no text: Accessibility, Secure Input, or elevation.

The text lands in the wrong app or the wrong field

VoiceSnap Pro targets whatever had keyboard focus at the moment you pressed the key, and it holds that target for the whole dictation. If the text went somewhere unexpected, focus was somewhere unexpected when you started.

The common causes are clicking into another window while speaking, a notification banner or system dialog stealing focus mid-dictation, and a page that was scrolled but never clicked into so no field had a cursor at all. Watch the app name on the pill before you speak — that is exactly what it is for.

• Click into the destination field and see the cursor blinking before you press the key.
• Do not alt-tab or click while a dictation is running. Press Escape and start again instead.
• In a multi-monitor setup, the focused window is not always the one under your mouse.
• If the text went somewhere you cannot undo it, the words are still in the notes library — open it with Control + Option + L and copy them out.

The first word or two is missing

This is nearly always the microphone opening late rather than VoiceSnap Pro starting late. Some inputs — particularly Bluetooth headsets and Windows devices with driver-level enhancements — need a moment to switch into recording mode, and any speech during that moment is simply never captured.

The habit that fixes it costs nothing: press the key, wait for the pill, then speak. Half a second is enough.

• Turn on the start sound in Settings → General so you have an audible cue rather than a visual one.
• Windows: Settings → System → Sound → your input → turn off audio enhancements, which can ramp the gain over the first half-second.
• Switch from a Bluetooth headset to a wired one and see whether the problem disappears — it usually does.
• In Settings → Audio, increase the pre-roll buffer, which keeps a fraction of a second of audio from before the key press.

Permissions stopped working after an OS update

macOS re-evaluates Accessibility and Input Monitoring grants when an app's signature or path changes, and a major system update can invalidate them even though the switch still looks on. The symptom is distinctive: everything worked yesterday, the toggles look correct today, and nothing types.

The fix is to remove and re-add rather than to toggle. In System Settings → Privacy & Security → Accessibility, select VoiceSnap Pro, click the minus button, then add it again with the plus button and pick it from Applications. Repeat in Input Monitoring, then quit and reopen VoiceSnap Pro. Restart the Mac if it still refuses.

• Moving VoiceSnap Pro.app to a different folder has the same effect as an update — the permission follows the path.
• Running it from a mounted disk image rather than Applications guarantees this problem, because the path changes every mount.
• Windows loses microphone access less often, but check Settings → Privacy & security → Microphone after a feature update.

Text arrives garbled, out of order, delayed or truncated

This is an insertion-speed problem, not a transcription problem — the words are right in the notes library and wrong in the field. Some apps drop or reorder characters when they arrive faster than a human could type: certain Java-based editors, remote-desktop sessions and older Electron builds are the repeat offenders.

Switch that app to clipboard insertion in Settings → General. VoiceSnap Pro then puts the text on the clipboard, sends one paste keystroke, and restores your previous clipboard contents. If you would rather not involve the clipboard, the same pane has an insertion-speed slider; slowing it down fixes most apps at the cost of a slightly slower paste.

• Compare the note in the library with what appeared on screen. Identical means transcription is fine and insertion is not.
• Try the same dictation into a plain text editor to confirm the app is the variable.
• Terminals with bracketed-paste enabled sometimes need clipboard mode rather than typed insertion.

What to send support

If none of the above fixed it, Settings → General → Copy diagnostics puts a summary on your clipboard: app version, OS version, input device, insertion mode and the permission states. It contains no dictated text.

Send that along with the four things that narrow a bug down fastest, and there will usually be no need for a second round of questions.

• The exact app and window you were dictating into, and whether it was elevated or remote.
• Which of the three checks failed: no pill, no meter, or wrong app named.
• What appeared on screen versus what the notes library recorded for the same dictation.
• Whether it happens everywhere or only in one app, and whether it started after an OS update.