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
NullPointerException #2083
Comments
Does this happen all the time or only sometimes? What version of Lottie are you using? Can you attach your animation? I don't think your suggestion will fix this issue. The stack trace indicates that an |
Hi @gpeal, we still have this NullPointerException on some less common Android devices, and judging by the numbers I suspect on certain hardware it crashes every time. We've been able to narrow it down to one of these four animations. I've pasted a full stacktrace as well. This is using 5.1.1. In this case the device was a Xiaomi Mi 9T running Android 10. java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference Thanks for your help. |
It isn't clear why the underlying issue is happening but if it's isolated and device specific, it's easier to add this harmless checking code rather than get to the bottom of this one. Fixes #2083
Hey @gpeal thanks for the fix. When can we expect this to be a part of a release? Currently these crashes accounts to be the highest in our app |
@msaikrishna Should be soon! You can use a SNAPSHOT or compile your own release if it's an emergency. |
how to get SNAPSHOT version,thanks |
Add the |
Hi @gpeal , I am getting NPE in 6.0.0 version also. Upgraded Lottie version in my Android app from 4.1.0 for the same issue. Checked it on Android 10 and 12. What shall I do?
|
hi @gpeal, I had the same issues, affecting user on Android 8.1, 9, and 11. these errors are being captured by firebase Crashlytics and Sentry
line 244
line 241 Android 7, 9, 11, 12
Can we add the null checking for the lines above just like what had implemented below?
Originally posted by @aliceInWahed in #1650 (comment)
The text was updated successfully, but these errors were encountered: