# Filemaker Go Crashes every time I use Voice to text **URL:** \ **Category:** Floating Topics\ **Tags:** filemaker-go\ **Created:** [April 29, 2025, 7:49pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834 "2025-04-29T19:49:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [April 29, 2025, 7:49pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/1 "2025-04-29T19:49:36Z")
Whenever I use voice to text on Filemaker Go on my iPhone (both latest versions) it hard-crashes Filemaker Go... is this a "known issue" that will be fixed in the future? Is there a work=around? Does anyone actually use Filemaker Go? lol 😂 ---
**Author:** ![MonkeybreadSoftware](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/monkeybreadsoftware/32/361_2.png) [@MonkeybreadSoftware](https://the.fmsoup.org/u/MonkeybreadSoftware)\ **Post date:** [April 29, 2025, 8:13pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/2 "2025-04-29T20:13:17Z")
Do you see a crash report? Or some messages in Console.app on a connected Mac? ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [April 29, 2025, 8:18pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/3 "2025-04-29T20:18:48Z")
ohh... Never done this before so I might be doing the wrong thing but I just tried the following steps: 1. Plugged phone into Mac using USB-C cable 2. Said "TRUST" and typed in my password 3. Opened an app called Console.app 4. clicked "start streaming" in console app 5. went back to phone and did the voice to text - crash thing RESULT: Nothing shows up here: ![CleanShot 2025-04-29 at 16.17.38](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/e/e48a36f53ad4b55e28217bc6c2879db8cb6a79f3.png) ---
**Author:** ![MonkeybreadSoftware](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/monkeybreadsoftware/32/361_2.png) [@MonkeybreadSoftware](https://the.fmsoup.org/u/MonkeybreadSoftware)\ **Post date:** [April 29, 2025, 8:38pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/4 "2025-04-29T20:38:47Z")
No messages sounds like the streaming of messsages didn’t get enabled. Do you have Xcode installed? There is a devices window where you could pick the iPhone and Xcode may enable something. ---
**Author:** ![weetbicks](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/weetbicks/32/206_2.png) [@weetbicks](https://the.fmsoup.org/u/weetbicks)\ **Post date:** [April 29, 2025, 8:40pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/5 "2025-04-29T20:40:20Z")
This was a known issue in Go 20 ([Claris Community (English)](https://community.claris.com/en/s/question/0D5Vy00000OV7arKAD/filemaker-go-crashes-when-users-dictate-into-a-field-with-the-iphone-microphone)) Make sure you're on the latest OS and version of FileMaker Go ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [April 29, 2025, 9:23pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/6 "2025-04-29T21:23:06Z")
OMG yeah that was the problem. Apparently they changed the name and there's an old app (which I have fully patched) and a new app (which I hadn't downloaded). All good now. ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [April 29, 2025, 9:26pm UTC](https://the.fmsoup.org/t/filemaker-go-crashes-every-time-i-use-voice-to-text/4834/7 "2025-04-29T21:26:45Z")
Oh no, I don’t have Xcode installed in this machine. But embarrassingly I did have an old version. I didn’t realize there were two different apps and so I just made sure my app was fully patched.