You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
validating FileId failed: size 32 for BaseUint32z as base type in definition message is greater than size 4 for BaseUint32z as base type from profile
#88
Open
tcortega opened this issue
Apr 29, 2024
· 3 comments
Been getting this error when attempting to read my fit file. Websites like https://www.fitfileviewer.com/ can read it just fine.
Here's it: https://fromsmash.com/klDheGo6hj-et
The text was updated successfully, but these errors were encountered:
definition message parsed: local: 0 | global: FileId | arch: BigEndian | fields: 5 | data dev fields: 0
parsed file_id message: {Activity Garmin 3113 0 2024-10-09 05:11:24 +0000 UTC 0 }
definition message parsed: local: 1 | global: DeviceInfo | arch: BigEndian | fields: 11 | data dev fields: 0
illegal definition message: local: 2 | global: Event | arch: BigEndian | fields: 6 | data dev fields: 0
parsing definition message: validating Event failed: field 3: size 8 for BaseUint32 as base type in definition message is greater than size 4 for BaseUint32 as base type from profile
definition message parsed: local: 0 | global: FileId | arch: BigEndian | fields: 5 | data dev fields: 0
parsed file_id message: {Activity Garmin 3113 0 2024-10-09 05:11:24 +0000 UTC 0 }
definition message parsed: local: 1 | global: DeviceInfo | arch: BigEndian | fields: 11 | data dev fields: 0
illegal definition message: local: 2 | global: Event | arch: BigEndian | fields: 6 | data dev fields: 0
parsing definition message: validating Event failed: field 3: size 8 for BaseUint32 as base type in definition message is greater than size 4 for BaseUint32 as base type from profile
Been getting this error when attempting to read my fit file. Websites like
https://www.fitfileviewer.com/
can read it just fine.Here's it: https://fromsmash.com/klDheGo6hj-et
The text was updated successfully, but these errors were encountered: