Broken animations on Android
Description
Broken animations on some android devices. The problem happens as soon as the app start.
rive-react-native 9.3.4 Device LG Q7+ Android 8.1.0
https://github.com/tiago138/rive-error
Screenshots
https://github.com/user-attachments/assets/68f2ccca-b205-4ec7-a983-f055c973bc32
Additional context
Other users have reported some similar problems.
Thanks for reporting, @tiago138. Do you know of any other device models that have this issue besides the LG Q7+?
One of my customers reported the same problem when I upgraded to the Rive renderer.
The phone used is a Samsung Galaxy S23, I reached out to them to get the OS version, I will update it here if they answer.
https://github.com/user-attachments/assets/a51754c5-5b4f-4798-9259-78ed32a319f0
(rive animations are supposed to be displayed in the carousel too)
When testing the app I notice the problem and never put it in production, so I donΒ΄t know of any other devices where it may be happening, because this was the only one where I tested it and had the problem.
Hey, I am on Samsung S24 FE, ONE UI 7 and has the same issue. Let me know if there any more information needed to fix this issue and I am happy to provide.
Hey, I am on Samsung S24 FE, ONE UI 7 and has the same issue. Let me know if there any more information needed to fix this issue and I am happy to provide.
Do you have this device? can you test my repo?
A rendering fix has landed and will be out in the next Rive Android release, and then we can update Rive React Native.
It has not been confirmed whether it resolves both of these issues, but it solves a rendering glitch similar to the above.
Thanks for the update @HayesGordon π
@HayesGordon is that supposed to be in rive-android 10.2.1?
I just tested it on https://lambdatest.com Samsung Galaxy S24 Plus with Android 15 emulator and it doesn't render at all for me.
Here is the repo you can reproduce with: https://github.com/benawad/android-rive-render-bug
Gotten users complaining about it not rendering on the following device models:
SM-S721B
SM-S926B
SM-A566B
SM-S721U
SM-S721U1
SM-S921B
SM-S721W
octopus ("IOS")
This is what it should look like when working correctly:
@HayesGordon is it possible to publish a new release and bump the android SDK so everyone can test if this fixes the issue by any chance?
@christophemenager if you want to test the Android SDK right now, you can stick this in your package.json:
"rive-react-native": "https://github.com/benawad/rive-react-native"
@christophemenager long time no see π were you able to confirm this fork and new rive-android runtime version fixed the glitch issue on specific android devices?
@benawad thanks for sharing the reproduction and devices. Sorry for the late reply, I've been out.
I'll take a look into this soon. We have been tracking another issue which stopped us from updating React Native.
Hi, May I know if the issue has been resolved? This is currently affecting production users in the latest app roll out. Also, could you please advise on the timeline for the fix rollout?
Appreciate your prompt response
Thank you.
@desmondtham-uf it has not. We had to rollback to 8.3.0 (uses the Skia runtime) to avoid Android users having problems
@benawad ahh alright. thanks for the update! However i cannot rollback due to the riv depending on View Model and it's too much hassle to remap using inputs. :/
@HayesGordon would you have any update?
rive-react-native hasn't been updated since 1 month ago, while rive-android had 3 updates in the same period
Would you know if the releases of rive-android might cover this issue?
Thanks in advance π
@rlods yes! We just made a release yesterday which addressed an issue we wanted fixed in the core Android runtime before bumping React Native. We will make a release soon.
@christophemenager long time no see π were you able to confirm this fork and new rive-android runtime version fixed the glitch issue on specific android devices?
Hey @rlods π I was away from home, sorry for the late answer. I never got a reply from the user having this issue so I have no easy way to reproduce unfortunately π’ I plan to upgrade to the latest version once it's release and rollout a small percentage in production to test it.
The latest release is up, 9.4.0
This includes a big fix for Android where under some conditions a crash could happen when the native view is disposed. It will be very helpful to know if any of you are still experiencing rendering issues, if you do please provide us much information as possible.
Our rendering team is focussin on Android rendering issues this month.
I will test it this weekend
@HayesGordon if you compare this video with the old that I had sent here you will see that the flashing is gone but the assets are broken.
It seems some improvement was achieved in solving this issue.
https://github.com/user-attachments/assets/b8a68a27-708b-466a-9095-14f68f15ad26
@tiago138 thanks for following up. This is on this device?
Device LG Q7+
Android 8.1.0
@HayesGordon I saw that the version 9.5.0 fix an issue with the Mali T720 and my device uses the Mali-T860 MP2. After testing it seems to be working as expected. Some times a quick glitch happens but it is not every time the animation plays but it is barely noticeable.
https://github.com/user-attachments/assets/4648e0a0-977e-46e5-b667-31f5d2c092a5
@HayesGordon I saw that the version 9.5.0 fix an issue with the Mali T720 and my device uses the Mali-T860 MP2. After testing it seems to be working as expected. Some times a quick glitch happens but it is not every time the animation plays but it is barely noticeable.
az-recorder-20250813-140919_xoDrOB3i.mp4
That's good news @tiago138, I'll share the above with our rendering team.
@benawad could you confirm if you're still seeing issues? We've not been able to reproduce the issues that you shared using the latest releases.
@HayesGordon I upgraded to 9.5 and sent the build to a user who had issues and it renders blank
Here is the device he has:
@HayesGordon I upgraded to 9.5 and sent the build to a user who had issues and it renders blank
Does the views have a width and height? I had a similar issue and solved adding it.
@tiago138 yes