-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
sporadic app crashes when picking a custom emoji during post creation #328
Comments
This is seems also to be an issue with megalodon. See here: sk22#920 |
I can confirm similar behavior when using the emoji picker or @ mention search. Usually it is triggered if I invoke the emoji picker with :, start writing the name of an emoji, and then start deleting text. It is guaranteed to crash if I fully dismiss the picker bar by deleting all text, and then shortly after invoke emoji search again. Here's my logs:
|
Can confirm it's still happening 2.3.0+fork.105.moshinda (105)
|
I love recycler views :) |
First some words on my setup. My instance runs akkoma on the stable branch and moshidons seems to do really great normally.
Describe the bug
The app tends to sporadically crash when I type in a shortcode for a custom-emoji. Normally I don't type out the whole name of the emoji but for a blobcat I would use something like :blob and then pick the correct emote I want. Sometimes but not reliably the app would crash for me. Funnily enough the app now that I am writing this report refuses to crash because of course lol.
To reproduce
Steps to reproduce the behavior:
Does this happen in the official app?
There is not really an official app for akkoma and mastodons app is not really usuable for this. I did not try megalodon though. The function does work as expected on the web-frontend akkoma-fe though.
Version
Moshidon version: [e.g. v2.1.4+fork.103.moshinda]
Crash log
btw thank your for adding the ability to collect crash logs so easily ❤️ This one is the most recent I got. i wanted it to crash again before posting just to be safe but it kinda is behaving atm.
The text was updated successfully, but these errors were encountered: