-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
[Bug] Animated .png emotes don't render correctly #3631
Comments
Can reproduce, logcat is spammed with |
|
Yes, definitely a bug, downgrading to 2.23.0 fixes the problem, but upgrading to 2.25.0 does not. Will report to the maintainer. Should we downgrade in the meantime? |
I agree with a downgrade if it fixes the problem. Seems like a reasonable thing to rev a new beta over. |
+1 for downgrade - was there a particular feature we upgraded for? |
Bug report: penfeizhou/APNG4Android#188
No, it was auto-upgraded by Renovate |
I noticed that animated .png emotes / emojis don't render correctly in the Tusky nightlies. They either don't render at all, or they're not the size they should be. They are never animated. In the current stable Version (21) they render as they should, and animated .gif emotes are always rendered correctly, in both versions.
Some screenshots, the :ablobcatrainbow: emote (animated .png) failed to render, while :confusedlucy: (a .gif file) renders just fine. When I started taking these, the emote wouldn't show up at all, but after moving through a few pages and refreshing posts here and there I started seeing the "broken and scaled up" version of the emote.
link to the toot
:ablobcatrainbow: file
:confusedlucy: file
Please LMK if there's any additional info you need! Thanks for looking into it.
Tusky Version:
Android Version: Android 12 / OneUI 4.1
Android Device: Samsung Galaxy s10e
Mastodon instance (if applicable): definitely happens on corteximplant.com, but I'm not sure if it's limited to our instance.
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
The text was updated successfully, but these errors were encountered: