• State Verified Answer
  • Replies 4 replies
  • Subscribers 10 subscribers
  • Views 228 views
  • Users 0 members are here
Options
Related

Help me! fit swift sdk parse fit file failed-compressedTimestampNotSupported FITSwiftSDK.Decoder.DecoderError error 3

8116604

When using the latest FIT Swift SDK (versions 21.184.00 and 21.171.0) to parse a FIT file,

an error FITSwiftSDK.Decoder.DecoderError error 3 is reported.

The exception message is compressedTimestampNotSupported.

Help me, how can I resolve this issue?

Urgently seeking assistance from technical experts.

  • 0

    Looking at the file you posted in Github, we have seen this behavior before with files from this manufacturer. When the ”data” field is used in the Event message only one byte of data is written to the file. The "data" field is defined as a uint32, so four bytes of data should be written to the file. So the file is malformed.

    There is a work around in the other SDKs to account for this behavior. The problem with the workaround is that it quietly ignores the error, which makes it difficult to know that the error exists. We will update the Swift SDK in the next few weeks with a similar workaround for this type of malformed file.


  • +1 in reply to Ben FIT

    We released an updated Swift SDK that can better handle the malformed files from this device manufacturer. It is version 21.187.0. Let us know if it solves the issue for you.

  • 0 in reply to Ben FIT

    Wow, you're incredibly efficient! You're absolutely my hero. I'll try this version first thing when I start work today. Thank you so much!  

  • 0 in reply to Ben FIT

    I tried the latest version and it has been resolved, that's great, very excellent,thanks a lot.

    Additionally, if the parsing speed of fit files could be optimized later, that would be even more excellent, very much looking forward to it.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries