This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New bug in FIT files: empty File ID and no Record messages

At www.fitfileviewer.com, I received many similar corrupted FIT files in the past weeks. I have not seen this type of corruption before, so I assume it is a bug in a recent software update on some devices. Typical for this corruption is:

  • There is a file_id messages, but all values are invalid
  • Many messages are missing, most notably the record messages, but also event, device_info etc.. Summary messages, like activity, session and lap are there. 
  • In several cases, but not always, many messages are duplicates, e.g. there are two identical activity messages, each lap and session appears twice.

FIT File Viewer can now fix these files, i.e. make it possible to import them in Garmin Connect, but of course it cannot restore the missing data.

I have seen this happening on FR 255, 955 and 965, and also in these threads:

  • However this link talks about fit files recorded on a non Garmin device and manually uploaded. This is not the case in this ticket. We're talking about fit files recorded by a Garmin device

  • thank you so much! I extracted the fit file and garmin immediately does not let me upload it until i put it through fitfileviewer. Wish I knew about this earlier. This has happened about 4-5 times on Enduro 2 

  • Ok this is now happening on the daily.. Many duplicate messages. Even lost a PR Disappointed One remark that i foprgot before. I have the FR255 AND a HRM Pro. Does everyone have a heartstrap as well ? Could there be any correlation?

  • Will Garmin respond to that ? It’s sad that they keep being silent on this matter 

  • I have a Polar H10, but I only ever use it for running, however this also happened to me on a walk, so there's probably no correlation.

  • This is a user forum, Garmin employees are seldom commenting it. They certainly don't read it and then go "oh, let's fix this". Even in the magical case they're actively investigating this we might never know it. I mean there's not a big chance they'll fix this, but even then they might just add a "fixed various issues" in the changelog. For that reason, everyone reading this that had the issue at least once should report it directly to Garmin Customer Support: https://support.garmin.com/en-US/ And also it's important to emphasise to them that we want them to open a ticket (it's in an system only Garmin employees can reach) for this to be finally fixed, and not interested telling us to use the http://fitfiletools.com 3rd party app as a workaround (even more, that it doesn't 100% fix it, we're loosing data that way) 

  • This thing started on my Fenix 7 Pro Solar Sapphire (v. 23.18) maybe a week ago. I'm also using HRM Pro Plus. Half of my activities are corrupted.  

  • Is there any chance that for the 'half of the activities' you used a route/routing option in your Garmin? That has been a reoccuring issue for many of us.

  • Hmm, I dont think this fully correlates. Some of the corrupted activities were Bouldering -- without any structured workouts or GPS. 

  • Update on my situation … Garmin has replaced my 965 twice for this issue and I’ve used the third one for 3 weeks now.  I do 3 to 15 activities per day, mostly indoor and outdoor Run, Walk, Yoga, and some sports.  I’ve immediately installed every software/firmware update. So far, the FIT file corruption issue has not recurred for Run activities (outdoor and Treadmill), however it occurred twice this week for Indoor Walking on a treadmill.  It did not occur for Indoor Walking not on a treadmill.  I’m going to continue using the replacement 965 but limit the length of time of indoor walking on treadmill in case I need to do the activity again, to maintain streaks for badges. I’m doing the same for other activities: limiting them and splitting them into 20 min, 30 min, 1 mile, etc. increments so I can easily repeat them if needed.  Step count has never been affected when the FIT files gets corrupted.