Layout Issues in iPad

Hi all,

IOS 18.0.1
MM APP 2.21.0
MM Server 10.1.1

Since a few versions behind I started facing issues with the ios app in iPad that are making the use of MM difficult.

  1. when typing a message, the keyboard covers the textbox and we cant see what we are typing.

  1. when using split screen, when you open the menu in a message, the menu is displayed completely off.

I appreciate if you guys could have a look at this.

Cheers

Hi @RbDev, thanks for bringing this to our attention! We’re sorry you’re experiencing these issues on iPad, and we recommend checking out our mobile app troubleshooting guide while we investigate further. Feel free to update the thread if the problem persists after trying any of the steps mentioned. Cheers!

I created a Jira ticket for the team to have a look at the split-screen issue. Thanks for flagging this @RbDev.

I was not able to reproduce the hidden keyboard issue, but I wondered if this is happening consistently for you or if it’s sporadic?

1 Like

Hello Matthew,

Excellent news. Jira ticket is the second stage.

In regards to your question. To replicate the keyboard issue. you need first to enable split-screen. Then move it full screen and you should have the issue.

Cheers

1 Like

I found another issue. Pictures are not being displayed when MM is set to split screen 1/4 (same size as iphone).

Another big issue l I really appreciate if you could sort this out.

@RbDev just letting you know that the latest mobile app should resolve the problems you identified above with split view.

Are image attachments just not showing at all on 1/4 size? I’m not able to reproduce this one. Can you test the latest release and let us know if it’s still an issue?

hello @matthewbirtch ,

It is looking much better now. the keyboard issue is sorted and the mm layout is working on different split sizes.

The only issue I see is when changing sizes from 2/4 to 1/4 all pictures remain 2/4 size and they go out of the screen.

Thanks for confirming those issues are fixed RbDev. I’ve logged this issue as well: Jira