Acknowledged
1 month ago

Connect IQ fields are missing on Lap view on API Level 5

Since the update to Api level 5 the Connect IQ fields disappeared from the Laps overview.

I've started a thread about this with more information and trying to figure out how to solve this.

I've tested with 2 api versions Venu 2 Plus (4.2.4) and Venu 3 (5)

 https://forums.garmin.com/developer/connect-iq/f/discussion/367311/connect-iq-fields-not-showing-in-the-app/

I hope this information helps. If not please let me know.

DopeyDwerg
  • 13 days ago

    I can also confirm that since my Forerunner 955 was updated to Api Level 5, Connect IQ values are no longer saved / displayed in the summary.
    They are still displayed for my activity on April 21, 2024 (connect.garmin.com/.../15001519169), but have not been displayed since April 27 (connect.garmin.com/.../15096521932). In between was the beta update of the watch to 19.xx with Api Level 5 (currently firmware 19.13).

  • 20 days ago

    I was reported very similiar issue by user of my app Padel AI. On his watch Fenix7x custom fields in Garmin Connect Stats tab are not being reported however it still works on my device Fenix7:

    Custom charts are working fine on both devices though.

  • 1 month ago

    Apparently it is possible to post images in the comments, and it's probably nice to have everything in the same place so here goes with the full post.

    This morning I played with my colleague same app version different api level versions. 

    These are my results (4.2.4) in the connect app all the fields are there. The landscape part of the image are the laps.

    As you can see there's Connect Iq showing

    This is what the Connect App of my colleague (api level 5.0.0) shows. In the red box should be the missing fields

    And this is the bit of code that's creating the fields

    session_field_game_score_player_1 = session.createField("game_score_you", FIT_GAME_SCORE_PLAYER_1_ID, Contributor.DATA_TYPE_SINT8, {:mesgType => Contributor.MESG_TYPE_LAP, :units => Ui.loadResource(Rez.Strings.fit_score_unit_label)});
session_field_game_score_player_2 = session.createField("game_score_opponent", FIT_GAME_SCORE_PLAYER_2_ID, Contributor.DATA_TYPE_SINT8, {:mesgType => Contributor.MESG_TYPE_LAP, :units => Ui.loadResource(Rez.Strings.fit_score_unit_label)});
session_field_game_time = session.createField("game_time", FIT_GAME_TIME_ID, Contributor.DATA_TYPE_DOUBLE, {:mesgType => Contributor.MESG_TYPE_LAP, :units => Ui.loadResource(Rez.Strings.fit_game_time_unit)});

session_field_stats_steps = session.createField("steps", FIT_STATS_STEPS_FIELD_ID, Contributor.DATA_TYPE_SINT32, {:mesgType => Contributor.MESG_TYPE_SESSION, :units => Ui.loadResource(Rez.Strings.fit_steps_unit)});
session_field_match_score_player_1 = session.createField("match_score_you", FIT_MATCH_SCORE_PLAYER_1_ID, Contributor.DATA_TYPE_SINT8, {:mesgType => Contributor.MESG_TYPE_SESSION, :units => Ui.loadResource(Rez.Strings.fit_score_unit_label)});
session_field_match_score_player_2 = session.createField("match_score_opponent", FIT_MATCH_SCORE_PLAYER_2_ID, Contributor.DATA_TYPE_SINT8, {:mesgType => Contributor.MESG_TYPE_SESSION, :units => Ui.loadResource(Rez.Strings.fit_score_unit_label)});

    Hopefully this information is slightly more understandable. If any more information is needed please let me know.