FIT file Developer Data looks correct but does not display in Garmin Connect

Hi guys - I am trying to encode a FIT file using my own platform and the files I produce look good in fitfileviewer.  However, when I upload the file to Garmin Connect, the developer data graphs do not display at all.  I think I'm really close to solving this puzzle, but cannot figure out how to find out what is missing from my file.  I have attached a sample output file from my tool.  This may help other developers who also encounter the same issue.

sampleOutput.fit.zip

  • Connect only displays developer data that was written to a FIT file by a Connect IQ app or data field. Even then Connect only displays the developer data that the developer has configured to be displayed. This configuration is part of the app bundle that is uploaded to the CIQ store. Connect does not display developer data written to the FIT file by 3rd parties.

  • Is this still the case?

    Any changes in the policies regarding requirements needed for showing developer data on Connect?

  • This is still the case. The only site I know of that displays developer fields is SportTracks

  • how garmin connect knows if a fit file belongs to the CIQ app? i mean I tried to fake the app uuid in the fit file, but the charts are still missing.

  • i mean I tried to fake the app uuid in the fit file, but the charts are still missing.

    The app in question needs to be:

    - uploaded to the CIQ store

    - built with the appropriate fitContributions metadata which matches the fields that you are writing. Connect uses this metadata to determine the strings to be used for the field label and units, among other things. Yes, the field name and units are also in the FIT file, but Connect only uses the strings in the metadata, as those strings are localizable (the dev can provide strings for multiple languages) and the strings in the FIT file are not. This metadata is only available for apps that were uploaded to the store (and obviously only Garmin can access it, not 3rd parties).

    Of course, 3rd party sites don't have access to this metadata and are forced to use the strings in FIT file.