FitContributor MESG_TYPE_LAP values don't appear in the Garmin Connect activity record

I have a data field that writes FitContributor MESG_TYPE_LAP values.

I call FitContributor.Field.setData(..) within onTimerLap() but when I look at the saved activity record in Garmin Connect Mobile or the web version, I don't see any of my values saved.

The data field was attached to a run activity and I ran a distance tha recorded multiple laps (km).

I downloaded the FIT file and converted to CSV and could not find my lap values written there.

Are FitContributor lap values just not visible in Garmin Connect at all? If they are , where?

Does the :nativeNum option have anything to do with this?

FlowState 12 days ago

This doesn't explain the problem you're seeing, but it's too late to call setData() for MESG_TYPE_LAP within onTimerLap(), unfortunately. onTimerLap() is called just after the previous lap has been recorded. That's why the SDK MoxyField calls setData() for MESG_TYPE_LAP fields every second. (It also calls setData() for MESG_TYPE_SESSION fields every second, but that's unnecessary and it would've been enough to only call setData() in onTimerStop()).

Keep in mind that setData() only sets the next value to be recorded, and has no influence on when a value is recorded, except for the fact that no data will be recorded until you call it for the first time.

Some other notes:

- to see FitContributor fields in Connect, your app has to be in the store (betas work)

- locally, you can use MonkeyGraph with your app IQ file and a FIT file to see FitContributor fields, although it's known to be buggy

- nativeNum shouldn't cause your fields to be hidden. Connect just ignores its presence completely, unfortunately (it's only good for certain data on certain 3rd party sites, and only when corresponding real native data is not present.)

As far as why you're not seeing data, there have been on and off reports about FitContributor data not showing up in the Connect app or website (usually one or the other, not both), but it for the fields to be completely missing from the FIT file sounds like a new problem.

Could be the same as this bug report:

[https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-iq-fields-are-missing-on-lap-view-on-api-level-5]

OttawaDeveloper 12 days ago

I have been using custom lap fields for years in an app. Has been working fine for me. Recently i hear reports of issues with it.

As far as i know some device models continue to work fine, but others with recent firmware updates seem to have issue.
So my guess is that my app is written correctly and some bug in the firmware of some devices may be causing issue.

In particular Forerunner models such with recent firmware updates like 18.22, and similar numbers.
There have been several updates with similar firmware versions for devices including FR165/255/265/955/965.
Another update 18.26 done about April 15, claims:

Connect IQ Bug Fixes and Improvements

I dont know if other models may be effected, Fenix 6/7 seem to have had some recent firmware updates, not sure if same issues.

Perhaps if people having issue with lap data in fitcontributor fields could indicate the device model/firmware version to see it this helps isolate the issue.

trudelta 12 days ago in reply to FlowState

Thanks for the detailed explanation. I found it is not working on Fenix 7, but is working on an Edge device, and a Vivoactive 4.

FlowState 12 days ago in reply to trudelta

Yeah sounds like the API level 5 bug. You could upvote it and leave a comment, hopefully it'll get traction soon.

InigoTolosa 12 days ago in reply to FlowState

Yess, I am quite sure this is the cause. I have been reviewing activities in the past recorded by an Edge1040. Anything related to lap fields works fine just till the first activity recorded after installing first beta firmware 20.xx supporting API level 5 in January. Since then, no lap info for CIQ fields is present.

flocsy 12 days ago

There might be 2 bugs related to laps. One when the IQ fields don't show up in the laps tab, and one that I have, where the headers are there but no data:

InigoTolosa 12 days ago in reply to flocsy

I guess the table structure is correctly created from the fitcontributors defined in resources. But it shows blanks because the corresponding values cannot be recovered from the fit file

OttawaDeveloper 11 days ago

this sounds like it may be related:

forums.garmin.com/.../fit-contributor-not-working-as-expected-on-edge-540-and-1040-units

OttawaDeveloper 11 days ago in reply to OttawaDeveloper

i searched and found 3 separate bug reports that appear possibly related. I have upvoted all of them, perhaps others would like to upvote them too.

https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-iq-fields-are-missing-on-lap-view-on-api-level-5

https://forums.garmin.com/developer/connect-iq/i/bug-reports/fit-contributor-not-working-as-expected-on-edge-540-and-1040-units

https://forums.garmin.com/developer/connect-iq/i/bug-reports/fit-contributor-data-not-showing-on-garmin-connect-web-or-mobile