{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieyhq2jyeeyihltggp4cmkk7vmlhcsrlggg5ums5g5nnfsbfm4d5m",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3miifka3mdy22"
  },
  "path": "/t/transcription-bug-in-the-app-is-still-a-thing/1378343#post_1",
  "publishedAt": "2026-04-02T02:11:21.000Z",
  "site": "https://community.openai.com",
  "textContent": "This bug has been going on (intermittently) for so long. It can’t be that hard to fix.\n\nChatGPT app on Android. I record some audio by clicking the mic, it thinks about it for a few seconds, then the input box goes blank.\n\nMost of the time it just works. In fact it’s worked every time for over a month, except for just now.\n\nIt’s super frustrating, because the chat is then broken. And extra frustrating because I’ve logged it as a bug a few times. It’s a black hole though, I don’t know if it’s been seen. I would assume that if it has been seen it could be fixed quickly, not ignored entirely and still be happening.\n\nI would have thought that OpenAI, of all companies, would have a system in place that passes such bug reports on to Codex, who will look at the code and reason about it and say “hmmm, yes on this line we assume that the returned payload has a property BLAH but if I look at the swagger docs for the transcription API I see that won’t be the case if it hits scenario BLAH and that would result in the attached image, so I’ll fix that and ask a human to review it. And in fact, if I look at the server logs for David at 12:55pm today I see the transcription request go through and see that it failed and returned that unexpected payload. Oh what a pity, we could have shown a ‘try again’ button so he didn’t have to speak all that out all over again”.",
  "title": "Transcription bug in the app is still a thing"
}