#Garmin express unexpected error code

And you can check out the code on github. I quickly hacked and bodged my way into a solution and then over the last few weeks I put some more effort into making a usable tool out of my quick hacking so if any one else encounters this problem there would be one more option to try and fixed it. The good news is that all of those things can be calculated from the existing unfinished file and appended to it. Moreover to be uploadable to Garmin Connect it needs to have a summary section, which was again missing in this file. To be considered a valid FIT file it needs to have correct header, some data records and a CRC at the end. It has invalid header and after some data records it ends abruptly. The file is broken, because it is unfinished. The solutionĪfter some investigation this is what I found: So lets turn on uber-geek mode and see what … can be done. I had done 3 hours and 100km on a trainer and had nothing to show for it. I tried to do something with garmin online fit repair tool but it gave an error straight away, and Fit File Tools which made the file uploadable to Strava but messed up the data.Īt that point all I had was one broken ride in Companion App, and no way to add the ride to my training score over at garmin connect, or brag about it on Strava. the judgement was always the same: ‘If the file is broken there is nothing to be done.’ I came to the Forum read a dozen of threads describing similar situations after Zwift crash or loss of FIT file, but given it’s hefty size of 434kB this should be the one.

Found two files one 0.6km long and another one that would not upload to Strava or Garmin Connect, or even validate as a. Screenshot_20210618-193130_Chrome 720×1480 33 KBĪt that point I decided to force quit Zwift and look into the local folders for some activity file and manually upload it there.