Lottie-ios: Expectations Breakpoint issue

[bishalg]

Check these before submitting:

• [x] The issue doesn't involve an Unsupported Feature
• [x] This issue isn't related to another open issue

This issue is a:

• [x] Non-Crashing Bug (Visual or otherwise)

Which Version of Lottie are you using?

Lottie 3.0

What Platform are you on?

• [x] iOS

What Language are you in?

• [x] Swift

Expected Behavior

• The application should not stop due to debug breakpoint

Actual Behavior

Application has enabled Debug breakpoint and there is Lottie animation on the start screen, hence the application will hit this exception breakpoint on each run.

Code Example

public init(from decoder: Decoder) throws {
    var container = try decoder.unkeyedContainer()

    if !container.isAtEnd {
      self.x = try container.decode(Double.self)
    } else {
      self.x = 0
    }

}

Animation JSON

https://lottiefiles.com/3015-man-and-phone

[bishalg]

Another Exception Breakpoint issue -

Screenshot

Code Example

required init(from decoder: Decoder) throws {
    let container = try decoder.container(keyedBy: KeyframeWrapperKey.self)

    if let keyframeData: T = try? container.decode(T.self, forKey: .keyframeData) {
      /// Try to decode raw value; No keyframe data.
      self.keyframes = [Keyframe<T>(keyframeData)]
    } else 

File Name
KeyframeGroup.swift

[buba447]

This is well known and unfortunately theres really no work around. This is how the codable container handles optional values...

[JoseG95]

I have the same issue with the KeyframeGroup. How can I solve it?

[oblq]

Have you tried decodeIfPresent()?
try? container. decodeIfPresent(T.self, forKey: .key)

This will not hit the Swift error breakpoint.

[jalone87]

Please consider this issue with a bit more priority, dynamic apps with heavy lottie usage at startup make it very annoying to run with a debugger attached.

[qazwyw]

Is this issus resolved?

[basheerpaliyathu]

stll not resolved