[BUG] Transcribed text no longer pastes automatically

Closed
  • Is something wrong?
#1,168 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #1193 by @mvanhorn — merged

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
audio-video-rtc, desktop

Research direction

Start by tracing the shortcut-key transcription flow in the macOS app and how it pastes the completed transcript; the issue does not name a file or test. Compare that flow with the menu bar’s “copy last transcript” action, then reproduce on v1.6.12-beta.1. Done when releasing the shortcut pastes the full transcript into the target application instead of only “v.”

Written by the indexing model from the issue text.

Description

bug
Describe the bug

Now, whenever I transcribe something while holding down the shortcut key, instead of pasting the entire text, it now only pastes in the letter "v." In order to get the text into the target application, I now have to do the extra step of going up to the menu item, clicking, going to "copy last transcript," and then pasting it into the area where it was originally intended. This all started to happen with the latest update.

Reproduction steps
  1. Open FluidVoice
  2. Recorde a transcription holding the shortcut key
  3. Release shortcut key
  4. Only a "v" is pasted instead of the entire text
  5. Use menu bar to "copy last transcript"
  6. Paste transcript into target application
Expected behavior

I just want it to work as it did in previous versions.

Actual behavior

Transcription is not being pasted

App Version

v1.6.12-beta.1

macOS Version

macOS 27

Architecture

Apple Silicon

Logs or crash report
Screenshots or screen recording

No response

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
2d 54m
Merged PRs (30d)
42

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.