Just want to let you all know we are working on a fix to improve the composer on iOS. Hopefully something should come out this week.
Sorry it’s taking so much time, I have been working a lot on this lately and trying various solutions internally, none is perfect so far, but Im getting close.
12 Likes
meta and my up-to-date instance both have same problem with “Save Edit” not responding if the keyboard isn’t collapsed, or needing the type cursor vertical line to be sometimes 1, sometimes many lower than where’s being edited.
1 Like
Im deploying meta with a version containing fixes related to iOS (not only the composer). Let me know how it goes for you, should be deployed one hour from 2025-11-18T23:36:00Z
Im not sure this is going to fix this, but it’s possible let me know if you still have it. And if you still have it, do you have it as often as before?
2 Likes
It seems to work as far as I can tell.
There’s another fairly recent issue where closing the keyboard makes the composer full screen. Previously, doing so would move the composer to the bottom half of the screen (roughly where the keyboard was), allowing me to view the post I’m replying to. Now I have to manually minimize the composer with the double down arrow button. Is this related to these recent iOS issues or should I submit a separate bug report?
1 Like
It’s a design-experiment
2 Likes
i still have it, though i can’t comment on how often yet
Looking forward to this going live. Discourse has been nearly unusable on iOS for many months now. And now typing this post on my iPad it’s perfectly fine— even though the compose panel is not maximized. So whatever you did, it worked.
5 Likes
Hopefully we merge this week 
but thanks for letting me know it improves things for you.
3 Likes
I usually don’t interact with Discourse via iOS, but gave it a go and for the most part, it is working as expected. 
To me this feels usable although, admittedly, I’m probably not familiar with all the ways it is/was not working correctly.
The only issue I found was the one already reported here which happens when switching to another app and when returning to Discourse — then the cursor is one line below where one is actually typing. Once that happens, it’s a little finicky to get back to normal state.
1 Like
it’s continuing to happen, after rebuild this morning
We have merged nothing yet, so a rebuild is expected to not fix anything.
1 Like
On my current tests on meta, this almost never happens anymore wether though the collapsing repro mentioned in the link post, or your note of switching from one app to another. I know it can still happen from time to time, especially on PWA, but I can only fix some of the bugs of apple 
and PWA is clearly the worst of all, direct browsing in safari or discourse app is less buggy AFAIK.
Note that I have plans, to fully revamp how the composer is displayed on mobile, but this is longer term plan, those fixes are mostly trying to extinguish the fires created by Apple, I also hope in the next weeks they will keep fixing more bugs.
FWIW, I only tested it using the Discourse app, and I can consistently reproduce the issue of switching to another app and returning. Sometimes the cursor looks to be in the right place, but when typing it’s actually not ok.
Anyhow, not saying this is a big issue, just reporting my experience. Let me know if I can be of help with more info.
1 Like
Meta still seems fine to me, no issues with the cursor being off a couple of lines from the typing spot and the reply button touch target is where it appears on screen, not an inch below.
