FIT contribution not updating

I updated the FIT contribution part of my data field recently, changing the title of the graph and units labels, and adding another contributed field.
I've verified that these changes are in the data field and on my watch, and that the recorded FIT file contains the new contributed field.
However, these changes are not showing up in the results on Garmin Connect (web or mobile) – the charts and values still use the old labels, and the newly added contributed field does not appear at all.

Indeed, digging through the scripts on the GC activity page using the developer tools console in Chrome reveals that the fit_contributions.json associated with the activity is the old one that is out-of-date. I verified that the latest one included in the .iq file I uploaded is correct, so it seems something broke when uploading a new version – the .prg update took, but not the .json.

Has anyone else seen this behaviour?
  • Well, in addition to this post, I contacted Garmin via the Developer section of the web site. I just got a reply directing me to this forum, as apparently this is the official support channel for Connect IQ! I thought this was more ad hoc, developers chatting, not necessarily Garmin support chiming in. Anyway, so, hopefully somebody from Garmin reads this thread and can comment upon this issue. Did another run today, all the information is in the FIT file, but Garmin Connect is using the wrong fit_contributions.json. :-/
  • Yes, the Garmin CIQ folks are active here. You can tell by their forum names. Those that end in .ConnectIQ are garmin people. Like Brandon, Brian and Coleman for example.
  • Hey,

    Thanks for reaching out to us. The forums are one of the best ways to get a hold of us. You can also email direct questions to the Connect IQ team at [email][email protected][/email].

    To be honest I'm not 100% sure that I know why this is doing this for you, but I have some suspicions and am reaching out to some other channels to confirm. It is possible that your data field was updated in the store, and the json was updated as well, but the local version of the data field is not up to date. If you use Garmin Express the data field will update automatically, if you are on iOS you have to choose to update, on Android there is still not an update button so you have to uninstall and reinstall with the latest version. It is possible that Garmin Connect is accessing a cached json associated with the app version you are using causing the wrong information to be displayed on Garmin Connect (still working on verifying this). If this is the case, you may just need to update the data field and things would work correctly. If you update the data field using one of the options above and still have the error, then the app store is likely not keeping the correct json. Either way, we have something to fix there! :o

    Thanks again for checking in!

    -Coleman
  • Thanks for the reply, and good to know re the email address.

    I have indeed verified that the local data field is the latest installed version (posted another thread about this, which enlightened me to the Android not auto-updated but reporting latest version number regardless issue), and have checked that, e.g. the FIT file has the newly added field, which it does.

    I have updated my data field a couple of time since first adding a FIT contribution, and Garmin Connect is still using labels for the first graph from the very first version I uploaded (and the second graph is not showing at all).

    I suspected something similar to what you write, that Garmin Connect is using a cached, out-of-date version of the FIT contributions JSON. I believe I have verified this using the developer tools in Google Chrome and digging through the JS files and such associated with an activity page on GC; indeed, the JSON it had loaded was the old one.

    If you need any further information from my end on this, let me know.
  • I can confirm this behavior. My labels and fields are not being updated.
    My app was in pending state when I observed this. I do not know it it also happens for already released apps.