Lottie rendering incorrectly on Android

[gitercn]

We are experiencing issues with Lottie animations displaying incorrectly on Android, while they appear fine on desktop. I recently opened an issue on iOS here: airbnb/lottie-ios#2417, and it was suggested that my issue might be similar to this one: airbnb/lottie-ios#2345, advising me to follow and track that issue. However, since I'm encountering a similar problem on Android as well, I'm opening an issue here too, hoping for a fix on both mobile platforms.

Checklist

1. My animation doesn't use any unsupported features. - Checked through lottiefiles.com and it tells me the no issues with the features used
2. I know what part of my animation doesn't work. - Yes
3. I have created a simplified version of my animation - Yes
4. I have attached the AEP file (as a zip file so it can be attached) that only has the part of the animation that doesn't work. - Yes

Describe the bug
The animation displaying incorrectly on Android

What version of Lottie did you test this on?
Tested with latest version of lottie-web 5.12.2, this looks good on desktop
Tested with the latest Lottie App on Google Play, 5.0.1, this looks incorrect
Tested with the latest LottieFiles App on Google Play, 2.9.49, this looks incorrect as well

What version of Android did you test this on?
5.0.1

Steps To Reproduce
Steps to reproduce the behavior:

1. Go to 'LottieFiles Android App'
2. Upload the demo.json Lottie Animation
3. See error

Screenshots
Looks good on desktop - Expected:

Looks incorrect on Lottie 5.0.1:

Looks incorrect on LottieFiles 2.9.49:

The zipped lottie json file
ziped-Lottie-demo.zip

[kudanai]

hello @gitercn

Can I quickly confirm two things:

• If exporting from AfterEffects (bodymovin?) works as expected?
• If the broken Lottie came through the LottieFiles pipeline (editor/workflow etc)?

Looking demo attached, I can see a bunch of "_render": True keys appearing in the Lottie, which is indicative of an incorrect export. This seems to have been a regression on LottieFiles for a minute there.

We've deployed a patch across the platform as well, so do give it another go now and see if the problem still persists.