Skip to content
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

Lottie animation freezes whole app on 4.4.0/4.4.1 (works fine on 4.3.1) #2329

Closed
ios-qonto opened this issue Mar 1, 2024 · 1 comment
Closed

Comments

@ios-qonto
Copy link

ios-qonto commented Mar 1, 2024

After migrating from Lottie 4.3.1 to 4.4.1 (and 4.4.0), we experience Lottie animations freezing whole app.

Which Version of Lottie are you using?

Lottie 4.4.1 (same behavior confirmed on 4.4.0)

Expected Behavior

(video from 4.3.1)

RocketSim_Recording_iPhone_SE_.3rd_generation._4.7_2024-03-01_14.45.52.mp4

Actual Behavior

Screen with Lottie animation is freezing when opening.
(video from 4.4.1, same behavior is on 4.4.0)

RocketSim_Recording_iPhone_SE_.3rd_generation._4.7_2024-03-01_14.33.00.mp4

Animation JSON

lottie_login_first_screen.json

Message in the console displayed after loading animation in 4.4.0 and 4.4.1

`transform.scale.x` animation for "Login-purple 4.Outer ring front 3.Transform" includes an After Effects expression (https://helpx.adobe.com/after-effects/using/expression-language.html), which is not supported by lottie-ios (expressions are only supported by lottie-web). This animation may not play correctly.

This message does not appear in 4.3.1, it has a different one:

Encountered Core Animation compatibility issue while setting up animation:
[Login-purple 4] The Core Animation rendering engine partially supports time remapping keyframes, but this is somewhat experimental and has some known issues. Since it doesn't work in all cases, we have to fall back to using the main thread engine when using `RenderingEngineOption.automatic`.
This animation may have additional compatibility issues, but animation setup was cancelled early to avoid wasted work.

Automatically falling back to Main Thread rendering engine. This fallback comes with some additional performance
overhead, which can be reduced by manually specifying that this animation should always use the Main Thread engine.
@ios-qonto
Copy link
Author

Sorry, closing this one as duplicate of #2330, I used company account instead of private one when opening this issue 🙏

@ios-qonto ios-qonto closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant