[Bug]: iPhone selected-text speech is not quieted when composer voice input starts
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- ios, react-native, typescript
- Ambito
- audio-video-rtc, mobile
Direzione di ricerca
Start by locating the native iPhone composer microphone and tracing how voice recording starts and ends. Check how the app configures iOS audio behavior during recording, then assess how selected-text speech interacts with that behavior. Done means the speech is appropriately lowered or paused while recording and any temporary volume change is restored afterward; confirm the desired pause or resume behavior with maintainers.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Before submitting
- I searched existing issues and did not find an exact duplicate.
- I included the observed workflow and marked details that have not been collected.
Area
apps/mobile
Steps to reproduce
- Open a thread with an assistant response in the native T3 Code iPhone app.
- Select text in the response and use the iPhone's Speak action to have iOS read it aloud.
- While that speech is playing, tap T3's microphone beside the composer to start voice input.
- Speak a reply while the selected text is still being read aloud.
These steps describe the reporter's observed workflow. Independent physical-device reproduction has not been performed.
Expected behavior
Starting composer voice input should lower or pause the selected-text speech so it does not compete with the person dictating. When recording ends, any temporary volume reduction should be restored; the appropriate pause/resume behavior needs maintainer confirmation.
Actual behavior
The iPhone keeps reading the selected text without an audible volume reduction when T3's composer microphone starts recording. The spoken response competes with the person's voice and makes the listen-then-dictate workflow difficult.
The reporter explicitly confirmed using T3's composer microphone, rather than the microphone on the iOS keyboard. No recording or transcript has been collected to establish whether the readback is captured or transcribed.
Impact
Interferes with listening to an assistant response and then dictating a reply in the same app. Frequency and transcription accuracy impact have not been measured.
Version or commit
Installed T3 mobile app version/build unknown. Exact revision has not been verified.
Environment
- Native T3 Code app on iPhone.
- iOS version and iPhone model not yet collected.
- Speech comes from iPhone selected-text Speak.
- Input uses T3's microphone beside the composer.
- Speaker/headphone route and selected transcription backend not yet collected.
Logs or stack traces
None collected. No confirmed root cause or proposed code fix.
Screenshots, recordings, or supporting files
None collected.
Workaround
No workaround has been verified.
Scope and related requests
This report concerns interference between existing iOS selected-text speech and existing T3 voice input. Adding built-in response read-aloud is a separate feature request discussed in #6762 and #33185.
Filed with the reporter's authorization using GPT-6.1 Sol in the Codex harness.
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 10h 56m
- PR unite (30g)
- 226
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pingdotgg/t3code
-
[Bug]: request_secret file delivery has no trailing newline, and the tool text does not say soForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 69/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Changing the sidebar project filter collapses an expanded Settled shelf back to 10 threadsAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
pingdotgg/t3code#34291 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 1 giorno
-
via-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
lingdojo/kana-dojo#33947 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
paperclipai/paperclip#20942 ·
I maintainer di solito rispondono entro 1 giorno
-
area: documentation good first issue package: rule-data status: accepting prs
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
status: needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
mastra-ai/mastra#30109 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno