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:

  • Do they tell you if it's a reconditioned or band new unit they're replacing it with?

  • My FR965 has been replaced twice for this issue and both times the replacement was reconditioned (looks/works like new).  The straps I got looked new.  The problem reoccurred after the first replacement, but has only happened twice in the 3 months since the second replacement (and several software updates).  I do 4 walk/run indoor/outdoor activities per day.

  • Do they tell you if it's a reconditioned or band new unit they're replacing it with?

    In another thread, I saw someone say that Garmin no longer replaces watches in the EU, because of legislation that says replacements under warranty can't be refurbished. The user was instead offered 25% off the MSRP for the recent Forerunner model of their choice (or something like that).

    To me this says:

    - Garmin never sends out brand-new replacements, only refurbished units

    - Garmin thinks the value of a refurbished unit is about 25% of a new unit

  • I've replied asking support if it'll be replaced with a recon or a new model.

    I've also asked if they can guarantee it won't have this issue. And if they can't, to tell me which models aren't affected.

  • I don't think they even know which models are affected, but even if they did, since this is a "relatively" new bug, it could easily be "added" to any other device, so I don't think the 2nd question will give you any information.

  • I had this issue yesterday with my 955, and I thought at first that this was because of my phone/watch connection. I went to remove/add my watch to connect app, only to have more issues with the recent iOS app update. Then after troubleshooting a bit by connecting it to my android phone which doesn’t have the connectivity issue, my recent activity still won’t sync. 

    That’s when I realized that there is something off with my watch and ended up seeing the corrupt .fit file. Fiddled around with it using the fit file viewer and saw the several errors, and Harry pointed me to this. It’s frustrating that it’s been months and this still isn’t fixed. I’ll contact garmin support, hopefully they’ll take a look. Shrug

  • Garmin support confirmed I would get a new watch -  not a refurb. My watch is less than 6 months old. 

    I asked if they could send one out before I returned mine - but they wanted a deposit of the full device cost. 

    I asked if they thought this was a hardware or software fault - they only advised they thought the new watch wouldn’t be affected. 

  • I think the deposit is a fair option. I would use it so I won't have a week gap in my data.

  • Another one with the issue here. It happened yesterday on a long run with my FR965. I've been going mad trying to figure out why I didn't sync until I've found this thread. The FIT file is there on the watch but corrupt and without the GPS data. Fit File Viewer fixed it to allow me to upload it but it doesn't count for any of the Garmin challenges or stats so extremely disappointing. It's the first time I notice this issue but I can't believe that this has been going on for so long without Garmin doing anything

  • because Garmin don't really know about it. The few dozens of people who might have reported didn't make it through. I mean there might be a few unrelated tickets opened, each seemingly only happening to 1 user.

    Please contact them at https://support.garmin.com/ and report it, and insist that they open an internal ticket and fix it! (Depending on which random agent you fall on they'll try to convince you it's not a bug or maybe point to fitfileviewer.com, but of course that is not even a viable workaround, as some data is lost)