Closed BurningDroid closed 7 months ago
My comment was for LottieAnimationView (xml)
You want to set your own failure listener because the default one will crash if the request fails. Try putting your phone in airplane mode and then triggering the request and you'll see a similar crash.
What you decide to do in the failure listener is up to you. You can show an error, a retry button, or whatever makes sense for your app.
Version Info
Description
I found a crash issue in my Crashlytics report. (Firebase) We use so many Lottie files dynamically, so I couldn't specify what Lottie file has a problem. But I think that this issue is not reproduced 100%. Is there any solution? or how can I find what JSON file has a problem?
Crash stack trace
Extra info
My app is calling the function
LottieAnimationView.setAnimationFromUrl()
. But it is only for developed XML UI, not Compose.But the crash occurred with Compose.