App locks up when tapping the message composer

[pixlwave]

Steps to reproduce

1. Run the app on iOS 16 on an iPhone 13 mini (probably others but I know this one works, tested on a real device and Xcode 14 simulator myself).
2. Open a room and tap the message composer to reveal the keyboard (make sure the keyboard shows on the simulator).
3. Type the following message but don't send it:

Doug
Test

Gggcv
Bbb

4. You might notice the composer is one line too high, but maybe not.
5. Navigate away from the room back to the hope screen.
6. Open the room again.
7. Tap on the message composer

Outcome

What did you expect?

To be able to continue typing

What happened instead?

The app locks up when trying to animate the keyboard onscreen in MXKViewController (the completion never gets called) and if left for long enough will crash.

Your phone model

iPhone 13 mini (device and simulator)

Operating system version

iOS 16

Application version

1.9.5

Homeserver

No response

Will you send logs?

No

[pixlwave]

Looks like the crash is an OOM one:

[JoshMock]

Similar experience here. iPhone 13 mini, and I noticed it on iOS 15 as well as 16.

[JoshMock]

Even killing/restarting the app doesn’t always work. And sometimes I can message just fine in some channels then it crashes on other channels, even when both are hosted on the same server.

[jedieaston]

Same. Shoot, is this why element is so buggy for me but not other people? My fun-sized iPhone?

[pixlwave]

Best sized iPhone 😉

[toshanmugaraj]

I can't reproduce in my iPhone 11 , iOS 16.0 , matrix sdk 0.23.18.

[rosston]

This happens to me on my iPhone 12 mini, iOS 16.0, Element 1.9.5. I didn't start seeing it until iOS 16, but I don't know for sure that that was the cause.

For me at least, I don't even have to go back to the main screen. Sometimes it freezes after I try to switch to the emoji keyboard (#6735). Other times it freezes after I take a break from typing for a second without exiting the room or app. Bug persists after deleting the app and reinstalling.

Not a complaint, just noting: this bug is so consistent for me that I've switched to FluffyChat on iOS (which doesn't have this problem) for the time being. I'm happy to be a reproducer or guinea pig if that'd be helpful!