-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android app stops repeatedly from emoji-picker screen #8252
Comments
We had the same problem in our instance. We couldn't pin the problem to a specific server or client version. The app also crashed randomly in specific channels and threads. But we figured out, that with disabled custom-emojis, the app no longer crashed. After disabling that specific emoji (and reloading the app with a sign-out and sign-in), the crashes stopped. We have no idea about the reason. The emoji was part of our instance for multiple years and there were not problems with it. The emoji was a gif. But other gifs are working fine. |
@Haliax would it be possible to share the offending custom emoji? |
@trystero11 you should be able to see your Mattermost Server version by going to Account Settings > Settings > About Mattermost in your mobile phone. Can you share the version? |
We see the same over here and have isolated at least one emoji that triggers a reproducible crash. App data must be deleted completely to recover from this. My os (graphene) creates a crash report with hardened_malloc and reports |
My Mattermost Server version is 10.1.1 (Build 11162711545). |
@octomike can you send the crash report and the custom emoji to [email protected]? Thanks! |
Summary
Android app stops on Pixel 9 Pro whenever I go to the emoji-picker screen
Environment information
Steps to reproduce
thumbs
). Mattermost stops. THIS IS THE BUG.Expected behavior
I expect to be able to search for emoji without the app stopping. I can do this without issues on the macOS and Windows desktop clients.
Other
I didn't have this issue with the Android client on my previous phone (Google Pixel 5), and it doesn't occur in the macOS and Windows desktop clients, so it might be specific to the Pixel 9 Pro (or Pixel 9s in general).
The text was updated successfully, but these errors were encountered: