FitContributor on Garmin Connect Mobile

Former Member
Former Member
What needs to be done to get FitContributor fields to show up on Garmin Connect Mobile?

As shown in the following activity, Garmin Connect web page displays all the FitContributor fields recorded by the IQ Dive Computer App: Depth, No Decompression Time, Ascent Rate, Ceiling, Gradient Factor, Max Depth. However, when the same activity is viewed on Garmin Connect Mobile, only the session fields (i.e. Max Depth) are shown. The graphs do not show up.

https://connect.garmin.com/modern/activity/1796279118

Thanks
Jesus
  • Former Member
    Former Member
    Sorry for the double posting. An error message was displayed when I submitted my previous thread, so I thought it did not go through.
    Jesus
  • The IQ dive computer is no longer listed in the store which is referenced in the activity link you gave. Without this it doesn't have the FIT contributor definition available to connect and probably won't work without it. It needs this information in order for the Connect site to display the developer recorded information. This would be my best guess.
  • Except that the FitContributor fields are displayed when viewed on the web, they are only missing in the app. This is probably due to the known iOS issue reported in the other (duplicate) thread, although Jesus has not responded to the question asking if he is using iOS or android.
  • It is possible/likely that is what is happening in this specific case but long term using side load applications not in the store for FIT contributor data should no be expected to work correctly (or at all) unless I have a fundamental misunderstanding of the way this works. This most likely works the way it does because the application is taking advantage of a previously stored FIT contributor definition and might work correctly with the iOS fix when completed. There are extensive issues with Connect and the FIT contributor implementation for the Connect website and mobile applications. My application records 34 FIT developer fields and they have different problems in each environment. Hopefully we'll see resolution to these over time.