After attaching an image in a chat, the attachment preview overlaps the keyboard, so I can’t see what I’m typing.
In the state shown in the screenshot (preview visible, input showing “Follow up…”), the keyboard does not come up at all. It looks like the app switched to a voice input mode.
The only way to recover is to force quit and relaunch the app.
Steps to reproduce
Open a chat in the Cursor iOS app.
Attach an image.
Tap the Follow up input and try to type.
Expected
The attachment preview sits properly above the keyboard, typed text is visible, and the keyboard opens normally.
Steps to Reproduce
Open a chat in the Cursor iOS app.
Attach an image.
Tap the Follow up input and try to type.
Expected Behavior
The attachment preview sits properly above the keyboard, typed text is visible, and the keyboard opens normally.
Hey, thanks for the detailed report and screenshot. I can see the state where the image preview is there and the empty “Follow up…” input is visible, but the keyboard does not appear.
I want to narrow down the trigger. Could you run two scenarios and let me know where it breaks?
Scenario A:
Force quit and restart Cursor.
Open an existing chat, but don’t tap “Follow up…” yet.
Tap “+” and choose one photo from the library.
When the picker closes, does the keyboard come up on its own?
Tap “Follow up…” and try typing a couple of words.
Scenario B:
Do the same thing, but first tap “Follow up…” so the keyboard is already up, and only then tap “+” in step 3.
For each run, please let me know:
whether the keyboard came up
whether you could see what you were typing
whether you used the microphone or dictation in that chat before attaching the image
A short screen recording of the moment when the input gets stuck would help a lot.
And if it gets stuck again, before force quitting, try swiping down on the small handle above the input, or switch to another chat and then come back. Sometimes that brings the keyboard back without losing the draft. Let me know how it goes.
Thanks for both recordings, they were really helpful.
I passed this to our mobile team along with your steps and recordings. This shouldn’t be happening, and it’s not something caused by your setup. I can’t give a timeline yet, but if I get an update, I’ll reply in this thread.
As a temporary workaround, if the input gets stuck again, try swiping down on the small handle above the input field or switch to another chat and then come back. Sometimes that brings the keyboard back without losing the draft, so there’s no need to force quit.
Let me know if you notice any other pattern, for example whether something specific seems to help prevent it from getting stuck.