Connect IQ Fields not showing in the app

I've got an app in the appstore Squasht It!, and at some point my Connect IQ fields stopped working. As in they won't show up anymore in the phone app.

And it seems to only be broken on the newer versions of the api. I've got a Venu 2 with api level 4.2.4 and I've got no problems but a friend of mine has a venu 3 and he has api level 5.0.0 and for him they're not registering anymore.

And for the life of me I can't figure out how to fix this. I've updated to the latest SDK and it does work when I create the fit file from the emultator.

Hope somebody can help me out. Since more people are starting to ask me what's wrong.

Top Replies

All Replies

  • Which SDK you used to build the current version in the store?

  • I think this was 6.2.0.

    I could release a new version with the latest SDK 7.1.0 my app doesn't seem to break with this SDK. 

    Do you think this could solve the problem?

  • It might solve it and it might introduce new problems. 

    What exactly is the problem? What does "they won't show up anymore in the phone app" mean?

  • They're not shown any more.

    <resources>
      <fitContributions>
        <fitField
    			id="0"
    			displayInChart="false"
    			displayInActivityLaps="true"
    			displayInActivitySummary="false"
    			sortOrder="0"
    			precision="0"
    			dataLabel="@Strings.fit_game_score_player_1_label"
    			unitLabel="@Strings.fit_score_unit_label" />
        <fitField
    			id="1"
    			displayInChart="false"
    			displayInActivityLaps="true"
    			displayInActivitySummary="false"
    			sortOrder="1"
    			precision="0"
    			dataLabel="@Strings.fit_game_score_player_2_label"
    			unitLabel="@Strings.fit_score_unit_label" />
        <fitField
    			id="2"
    			displayInChart="false"
    			displayInActivityLaps="true"
    			displayInActivitySummary="false"
    			sortOrder="2"
    			precision="2"
    			dataLabel="@Strings.fit_game_game_time"
    			unitLabel="@Strings.fit_game_time_unit" />
        <fitField
    			id="3"
    			displayInChart="false"
    			displayInActivityLaps="false"
    			displayInActivitySummary="true"
    			sortOrder="3"
    			precision="0"
    			dataLabel="@Strings.fit_steps_taken_label"
    			unitLabel="@Strings.fit_steps_unit" />
        <fitField
          id="4"
          displayInChart="false"
          displayInActivityLaps="false"
          displayInActivitySummary="true"
          sortOrder="4"
          precision="0"
          dataLabel="@Strings.fit_match_score_player_1_label"
          unitLabel="@Strings.fit_score_unit_label" />
        <fitField
          id="5"
          displayInChart="false"
          displayInActivityLaps="false"
          displayInActivitySummary="true"
          sortOrder="5"
          precision="0"
          dataLabel="@Strings.fit_match_score_player_2_label"
          unitLabel="@Strings.fit_score_unit_label" />
      </fitContributions>
    </resources>

    These are my fit-contributions but aparently none of these fields show up in the statistics or the lap screen.

  • Ah, so you meant Garmin Connect app. What about the web? Include screenshots of the places where they are supposed to be and aren't.

  • I see now similar problem in my DF, but not exactly the same:

    In this tab it's OK:

    Also the stats are here:

    But the laps is chaos:

    Fields name are there, but the values aren't. And there supposed to be 3 columns, but instead there are 6, each of them twice:

    Grapes are OK:

  • So it's not just only my app.

    I took 2 fit files and compiled some screen shots of it. 

    this is the one where it's still working

    You can see there's all the fields and everything filled correctly.

    this is the one where fields are not correct

    And also the data is corrupt. It's working for Session fields they're correct but the lap fields are completely messed up

  • R U sure it's a Garmin bug? To me it looks like the app writes -1 (signed int) and thinks it means "no data", but it's treated as signed int: 4147483647. IMHO either don't write data to steps when there are no steps or write 0, and it'll be ok. 

  • but steps should not be in that list though. Steps should only ben shown in Session. And there's the correct value reflected. So it's completely messed up. Also in the wrong file there's only 3 field_descriptions where there should be 6 like in the correct one. I think I'm doing something wrong in the definition of the lap fields, but I don't know what.

  • I don't understand you. You seem to mix different things. You started by "appstore Squasht It!" and "they won't show up anymore", so I assumed you have an app that was already working and that you haven't change it or at least not something in the fit recording part of it.

    Then you sad that it's not only your app. It's not clear whether the 2 images are from your app or from another app. (Nor what you don't like in them, 'cause you only wrote "are not correct" so I guessed that it's about the MAX_INT values)

    Then you wrote that maybe you're doing something wrong, so there I started to be confused. If this ap of yours never worked then it's an issue, if it did work and isn't working now then it's another issue.

    So is this a new app, that "just" doesn't work, or it worked in the past, and is now broken without your change?