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

TCX import is failing

I am attempting to import TCX files from Fitbit into Garmin and I am getting this error for every TCX file I try:

An error occurred with your upload. Please try again.

When I open Chrome's debugging tools, in the console I see this error after I click the "Import Data" button:

GET connect.garmin.com/.../4c37c9631b194ca78047829bc7194dd3 500 (Internal Server Error)

The TCX files are sourced directly from Fitbit so I have no reason to suspect they are not correct and I have done no modifications to them. I have tried both very small TCX files as well as larger ones. 

Can someone from internal Garmin support help with this?

  • That's weird as the XSD doesn't require the Author tag.... so if they are requiring it, it breaks their XSD.

  • I suggest you copy/paste the <Author> tag from my previous message into your Fitbit-generated TCX file and then try importing it to GC. If the edited file now imports successfully then we should feed this info back to product support so they can advise their devs.

  • I just remembered that I read somewhere about an app that modified .tcx files from non-Garmin sources to fool the Garmin import into thinking that a Garmin device created them. The purpose was to be able to get training-load and other metrics from non-Garmin devices. I read that the app recently stopped working.

    I wonder if Garmin changed the import process to block that workaround and inadvertently caused the problems we're seeing.

  • Perhaps. Seems more likely that the just want to know the tcx source and are mandating the <Author> tag for that purpose.

  • The Tip with the Author tag works fine with my Bosch E-Bile tcx files !!!

  • If you would like your Fitbit data to be in a format importable by Garmin (including the TCX files in a format they require), you can use this tool: https://fitbitjsonconverter.azurewebsites.net/

  • Genius! I've just tried this to fix the problem with not being able to import from the Keiser MSeries app for sessions on an m3i bike and it works a treat. I'd been scratching my head and trying to spot the differences in the TCX files from one exported from Garmin Connect, and one exported from mSeries. I had only been looking at the top of the file and the individual Track and Trackpoint entries and had failed to notice this change at the bottom of the file.

    Thanks for the solution!