iOS - blank content after thread answer or adding photos with text

[fpeterschmitt]

Summary

Each time i navigate in a discussion thread or try to upload more than one photo (after navigation), the app goes blank with only the "blue bar" displayed.

I have to restart the app completely in order to recover.

Environment Information

• Device Name: iPhone 7
• OS Version: 14.6
• Mattermost App Version: 1.44.0
• Mattermost Server Version: 5.36.0

Steps to reproduce

• Clean mattermost installation with no plugin
• No proxy whatsoever, i setup a fresh installation on a LAN. Please note that i have the same behaviour with or without a reverse proxy, and that this problem is happening for more than a year now.
• Configure the chat server to http://<local.ip>:8065
• Successfully access the team
• Send messages successfully
• Replying to a thread or sending more than one photo triggers the bug

Two things:

1. The bug seems to trigger when exiting the thread after tapping the input field (showing the keyboard). Even if i collapse the keyboard, the bug still triggers.
2. For photos, tapping the "add photo" button while having triggered the keyboard trigger the bug.

Expected behavior

Still being able to navigate in the application, see messages etc…

Observed behavior (that appears unintentional)

In order:

After login:

Replying to a thread:

Message successfully sent in thread:

Exiting the thread to view the entire channel:

Now switching channel:

Switching channel again:

After restarting the app:

[amyblais]

@josephbaylon Can you reproduce this?

[fpeterschmitt]

@josephbaylon Can you reproduce this?

If there is a possibility to install and test with a "debugging version" of the app, i'll be more than happy to do so :)

I don't have a Mac though so i doubt i could do that without testflight or alike.

[josephbaylon]

@amyblais I'm not able to repro this issue.

[amyblais]

cc @enahum if you have any thoughts on this.

[enahum]

This is the first time I'm seeing this, happening for more than a year? interesting... cause no one and I mean no one as had an issue like that.. Also I doubt is data driven as @leryan says he is seeing this on a newly installed server.

@leryan is this only happening to you on your iPhone 7? does it happen on other iOS devices or to anyone else using your deployment?

[fpeterschmitt]

This is the first time I'm seeing this, happening for more than a year? interesting... cause no one and I mean no one as had an issue like that.. Also I doubt is data driven as @leryan says he is seeing this on a newly installed server.

I also find this very strange indeed.

@leryan is this only happening to you on your iPhone 7? does it happen on other iOS devices or to anyone else using your deployment?

I'm alone having this problem, other iOS users have more recent iPhones than me :)

Could it be from the OS itself with consecutive upgrades?

If i'm alone having this, the chances it's from my device are quite high.

Any chance to get a debug build though?

[fpeterschmitt]

fyi, i've set zoom and text size to their default values, deinstalled the app, rebooted, reinstalled, and same behaviour. so it's not related to a "display" problem.

if having a "debug" build is impossible i'll reset the entire phone and retry 🤷

[enahum]

@leryan the best way to get a "debug" build is to clone the repo and run it in development mode.. "Debug builds" is not something that we can easily distribute

[fpeterschmitt]

I found the bug I think: in Accessibility parameters, Motion settings, enable "Reduce Motion" and "Prefer Cross-Fade Transitions"

It's 100% reproducible that way, and I don't have the problem if the last option is deactivated!

I did a full Settings reset on the phone and the motion effects jumped into my face, and i tried that. No need to reinstall the app.

[enahum]

@leryan in fact I was able to reproduce by enabling "Prefer Cross-Fade Transitions" on iOS 14 and iOS 15.

This seems to be a bug with the React Native framework facebook/react-native#31484 the issue is already opened and we would need to wait until it gets resolved.

[fpeterschmitt]

Ah thanks! I guess the issue can be closed then, as you wish :)