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

Library update from 6.5.2 to 6.6.0 cause crash #2568

Open
sakismts opened this issue Oct 29, 2024 · 2 comments · May be fixed by #2591
Open

Library update from 6.5.2 to 6.6.0 cause crash #2568

sakismts opened this issue Oct 29, 2024 · 2 comments · May be fixed by #2591

Comments

@sakismts
Copy link

After updating to 6.6.0 my app crashes with the error:
java.lang.NoSuchMethodError: No static method LottieAnimation(Lcom/airbnb/lottie/LottieComposition;Lkotlin/jvm/functions/Function0;Landroidx/compose/ui/Modifier;ZZZLcom/airbnb/lottie/RenderMode;ZLcom/airbnb/lottie/compose/LottieDynamicProperties;Landroidx/compose/ui/Alignment;Landroidx/compose/ui/layout/ContentScale;ZZLjava/util/Map;Lcom/airbnb/lottie/AsyncUpdates;ZLandroidx/compose/runtime/Composer;III)V in class Lcom/airbnb/lottie/compose/LottieAnimationKt; or its super classes (declaration of 'com.airbnb.lottie.compose.LottieAnimationKt'

works fine with 6.5.2

@gpeal
Copy link
Collaborator

gpeal commented Oct 29, 2024

@sakismts Can you attach a project that reproduces this?

@inorichi
Copy link

inorichi commented Nov 4, 2024

This is due to a binary incompatibility between 6.5.1 and 6.6.0 because a new parameter was added on that composable function.

Any code compiled against 6.5.1 or lower is not compatible with a 6.6.0 runtime version. You must ensure all your dependencies using lottie to compile against either of those versions.

But I'd suggest the lottie team to add the previous LottieAnimation signature that just delegates to the new one, because they added a breaking change in a minor version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants