Issues with Connect online and mobile display of data provided by FitContributor

Hello,

I am developing a datafield, it's late beta, could be published, but I encountered several issues with the display of data in Connect provided by FitContributor.
The datafield uses a couple of Fields with different message type to write data into the fit file of the activity.
While it seems that the data is written correctly, the display of the data is partly broken or wrong in Connect online and Connect mobile.
In one or the other app language is wrong (the datafield supports english as default and german language), or in one data is missing while it is present in the other, one displays String data correctly, the other shows Number instead, and so on...
Please review the screenshots I made, I have commented them.

Connect mobile is iOS version 3.22.2.8, just updated from previous Version, Activity was synced with previous version.

Thanks.
community.garmin.com/.../1258382.jpg community.garmin.com/.../1258383.jpg community.garmin.com/.../1258384.jpg community.garmin.com/.../1258385.jpg
  • Former Member
    Former Member over 7 years ago
    relatively soon?
    means wait another year at garmin,
    i'm just thinking of stopping free development for garmin :mad:
  • Former Member
    Former Member over 7 years ago
    It looks like a fix has been implemented for the 17.22 API release for an issue where we only store 1 CIQ data field for laps. Besides that it does seem like the ticket for this item has gone cold, we've reached out to see if there's been any further progress on it, sorry for the delay, we will update once we hear back.
  • Former Member
    Former Member over 7 years ago
    Men, this bug has existed for more than one year, possibly closer to two.
    It is evident there is very little interest in fixing this.
  • Former Member
    Former Member over 7 years ago
    Not displaying custom fields and graphs correctly is a pretty bad thing. How can Garmin allow this bug to exist for so long. This looks bad guys !!
  • Former Member
    Former Member over 6 years ago
    Hey all,

    I wanted to give an update here. There are multiple issues that were discovered in addressing this issue overall. I'm happy to report that we have one of them fixed and are working on the solutions for a couple of others. You won't see the fix yet as it has to be pulled into a future release. My guess is that it's likely all going to happen at once, but bugs getting fixes is always good news and I like sharing good news!

    Thank you for your patience,
    -Coleman