-
Notifications
You must be signed in to change notification settings - Fork 24
JSON files with similar animations render incorrect animation #21
Comments
Can you provide a reproduction? |
yes, use the files here - https://drive.google.com/open?id=1dAS6UYVpERsP0mmBBVblwHBKfHjFeGWj and try previewing them, you'll see that they show the same animation in the app but when previewed online, they are different animations |
I suspect the issue might be the way you're loading them - can you share that code? |
i first used the example from the package when i noticed the issue but here is the code i ended up with:
loadAsset
|
Just to help narrow this down, can you change
to
|
im actually loading them using your example and the bug is still present. any update on this bug? this package seems like my last hope ! |
I'm not able to reproduce your issue in a clean project. I would instrument your core and try to figure out where this is going wrong. |
I'm not too sure what "instrument your core" means. I created a new project and copy/pasted the example. Are you using the JSON assets linked in the above drive ? I've only had it happen with those two json animations. For clarity, they are two separate animations but if you load "Gongv4" it shows the animation for "timerv4". "Timerv4" animation works just fine |
Sorry, that should have been code not core. I'm suggesting adding print statements to make sure your actual assets are different. |
I have 2 separate .json files, both named uniquely in my assets folder.
Viewing them in an online Lottie previewer, everything looks correct. Both animations are different.
When I actually load the asset and run the animation in my project, it shows the EXACT SAME asset in both widgets. I can load alternate .json animations just fine, but i THINK since the 2 I'm using are so similar in looks, it some how is showing the same asset instead of the correct one.
Tried one of the other lottie packages that use platform view and the animations show correctly.
The text was updated successfully, but these errors were encountered: