Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[🐞 BUG] Dictation won't paste into any app no matter what copy setting I change

Open
#469 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, swift
Domain
desktop

Research direction

Start by tracing what happens after a dictation is recorded in history, focusing on the three copy modes named in the issue. Reproduce the intermittent failure on macOS 26.5.1 across apps such as cmux and Chrome. Done means dictation text is reliably inserted into the active app using the supported copy modes.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
When using FluidVoice it will not paste what I said into the app I'm in. This has happens almost every time I use the dictation feature. I tried it in cmux, google chrome, etc. 9/10 dictations don't paste into the app I'm clicked in. Looking at the history tab though it saw my msg and has it recorded there. I've tried changing the copy mode setting multiple times from "Copy to Clipboard" to "Clipboard Paste" and "Clipboard Free Insert". It worked flawlessly when I first updated to v1.6.0 and then randomly it just started acting up. Also tried updating to 1.6.1 and the issue still persists.

To Reproduce
Use dictation in any app, sometimes it just won't paste what was said.

Expected behavior
For what I said to be pasted into the app I was using.

Screenshots
If applicable, add screenshots.

Environment:

  • macOS Version: 26.5.1
  • App Version: 1.60 & 1.6.1
  • Architecture: Macbook Pro M2 Pro 16GB
Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 16h
Merged PRs (30d)
26

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.