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

Uploads to Garmin Connect failing.

Former Member over 11 years ago

Hi there,

So I've been for a run this AM with my new Forerunner. I returned and hit sync on the Garmin Express. It reports no errors and updated the sync time and claimed to send the activity. See below:

Garmin Connect has no record of the activity though. See below:

Trying to manually upload the *.fit file (of todays date, 13KB, from C:\ProgramData\Garmin\GarminConnect\Unknown ANT Device-3855991410\Upload\FIT_TYPE_4) just hangs indefinitely. See below:

Do you ladies and gentlemen have some sort of problem at your end?

Cheers,
Simon.

0 Former Member over 11 years ago

UPDATE: I have managed to work around the problem by running the .fit file through the Garmin fit file fix utility at http://garmin.kiesewetter.nl/ converting it to .csv and then back. I've attached the before and after files below.

After the conversion the second fixed file manually uploaded just fine. As the first file is exactly as extracted by Garmin Express from the Forerunner, if anyone from either the Garmin Express or Connect support teams are reading this I'd suggest you take a look at the files above to try to work out what the heck's up with your respective pieces of software. Or better yet: sack one of your engineers, find out who wrote the above site, and offer him a job.

0 travis.vitek over 11 years ago

It isn't the site that is the problem, is is your 310XT that is generating corrupt fit file (I've seen corrupt fit files on devices that have mounted filesystems, so Garmin Express isn't even in play). I suppose that it could be argued that the import routines should be able to take any old garbage and convert it to a valid .fit file, but I think we'll be able to agree that at some point this isn't possible without human intervention.

I think it is interesting that the device folder for your 310XT is named Unknown ANT Device-3855991410. I'm guessing that this is because your device name (in the device settings) is blank, but I'm not sure.