Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
On Grok Bot iOS, in-app voice transcription (the app’s own composer mic to text - not iOS keyboard dictation, not voice-call) often crashes the whole app mid-transcription.
Before realtime streaming text, this was a simple record then pause/submit flow and I never crashed. After realtime streaming text was added, crashes started. Short takes are hit-or-miss; ~5+ minute takes crash much more often. When it crashes, the in-progress text is gone and I lose my chain of thought.
I still prefer this feature and keep using it a lot. I don’t avoid it - but long takes are stressful now because a crash wipes the thought mid-stream.
I have never seen this kind of crash on ChatGPT’s voice/transcription. I haven’t tested long voice-call enough to comment on that. Device: iPhone 15. No Android to compare.
Starting point for debugging (hypothesis, not proven): the realtime streaming text path may lean on on-device / edge compute and RAM. I am on an iPhone 15 with limited RAM; stronger phones may not hit this as often, which could also explain why reports are sparse. Worth checking memory pressure / on-device ASR or streaming-text allocation first.
Steps to Reproduce
- Open Grok Bot on iPhone.
- Start in-app voice transcription in the composer.
- Speak for a long take (especially ~5+ minutes) while text streams live.
- App may crash mid-take; content is lost.
Expected Behavior
In-app voice transcription should not crash the app, and a failed take should not wipe the in-progress text.
Operating System
iOS
Version Information
Grok Bot iOS (build not captured in this report)
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor