crash: JsonUtf8Reader.nextInt

[MKelman]

Describe the bug
I am receiving this crash (full crash log attached)

Fatal Exception: java.lang.IllegalStateException: Unable to parse composition
at com.airbnb.lottie.LottieAnimationView.lambda$static$0(LottieAnimationView.java:72)
at com.airbnb.lottie.LottieAnimationView$1.onResult(LottieAnimationView.java:84)
at com.airbnb.lottie.LottieAnimationView$1.onResult(LottieAnimationView.java:77)

What version of Lottie did you test this on?
6.5.0

What version of Android did you test this on?
occurring on all android versions

Steps To Reproduce
Steps to reproduce the behavior:

1. go to https://app.lottiefiles.com/
2. make lottie
3. download image
4. when we upload that image and view it, there are decimals.. so we have to undecimal it?

stacktrace

com.adfone.aditup_issue_9ca65e77d3c3d036d7f1f31e48bb3ef8_crash_session_66F2F4BD0327000166560C71E2CFFAE2_DNE_0_v2_stacktrace.txt

example lottie file downloaded
blue_progress_bar_corrected.json

[gpeal]

That animation is parsing fine for me and the stack trace you provided doesn't seem to line up with the code in Lottie 6.5.0
https://github.com/airbnb/lottie-android/blob/v6.5.0/lottie/src/main/java/com/airbnb/lottie/parser/LayerParser.java#L242

As a result, it isn't clear to me which property you have that has decimals that is currently parsed as an int. Can you provide more information?

CleanShot.2024-09-28.at.23.02.57.mp4

[MKelman]

@gpeal I made a mistake, here is the bad json. I gave you the correccted, chat gpt json, that your website spitted out.

blue_progress_bar.json

If you look at the top layer of the crash,
Caused by l1.a: Expected an int but was 501.999 at path $.layers[10].h
at com.airbnb.lottie.parser.moshi.JsonUtf8Reader.nextInt(JsonUtf8Reader.java:815)

this ( com.airbnb.lottie.parser.moshi.JsonUtf8Reader.nextInt(JsonUtf8Reader.java:815)) occurs here https://github.com/airbnb/lottie-android/blob/v6.5.0/lottie/src/main/java/com/airbnb/lottie/parser/LayerParser.java#L242 and that

which seems like it doesn't like doubles? If you review the json i attached, its full of doubles in there. Does that makes sense

[MKelman]

Hi @gpeal have you been able to look into this?

[gpeal]

@MKelman Not yet! I support Lottie on nights and weekends but will do my best to find some time for this. Feel free to take a look yourself and put up a PR if you'd like though.

[MKelman]

Sounds good, appreciate it! Wasn't sure if the "needs more info" flag was the reason you didn't see this yet. If I get a chance, I'll try to look myself as well :) But let me be clear, I dont believe the issue may be on android, I believe it may be part of the web tool that spits out decimal place results. But I'll see what else I can find If i have the time

[gpeal]

@MKelman The second animation you attached also parses fine. I'm trying reverse engineer what your issue is and it still isn't clear:

1. Your stack trace points to LayerParser line 242 which is a break statement.
2. From the error Caused by l1.a: Expected an int but was 501.999 at path $.layers[10].h, I think it might actually be this line which is already parsed as a double.

Can you provide more info?

[JuHyang]

I encountered a similar issue, and after investigating, I believe the reason is as follows:

The root cause of the intermittent exceptions when parsing a double value like 796.05 in the nextInt() method likely stems from floating-point precision errors. In Java (and Android), floating-point numbers are not always stored with exact precision, especially for values with decimal places. As a result, 796.05 might be stored internally as something slightly different, such as 796.0499999... or 796.0500001..., which can lead to inconsistencies during parsing.

Here’s how these precision issues can lead to intermittent behavior:

Floating-Point Precision Variability
When 796.05 is parsed through Double.parseDouble(peekedString), it may be stored as 796.0499999.... Casting this to int will yield 796. However, if the parsed value happens to be slightly closer to 796.0500001..., the casted int will still be 796, but the comparison in nextInt() (result != asDouble) might fail, triggering an exception.

Inconsistent Comparison Results
Due to these floating-point precision issues, the comparison between the int-casted value and the original double can intermittently pass or fail, depending on how closely the parsed double aligns with its intended value.

These floating-point precision limitations seem to be the underlying cause of the intermittent exceptions.