FIT file empty for :subSport=>Record.SUB_SPORT_LAP_SWIMMING

hi,
is this a known issue (or feature)?
i am using fitcontributor to write data into a swim session.
i have realized that if i set
:subSport=>Record.SUB_SPORT_LAP_SWIMMING
the FIT file is empty. if i dont set the subSport, it works fine.


FIT empty:
session = Record.createSession({:name=>"Swimming",
:sport=>Record.SPORT_SWIMMING,
:subSport=>Record.SUB_SPORT_LAP_SWIMMING});


FIT OK:

session = Record.createSession({:name=>"Swimming",
:sport=>Record.SPORT_SWIMMING});
  • We currently have a ticket looking at this issue. A link to your post has been added for the investigation. Thank you again for reporting this.

    -Coleman
  • hi,
    i was in contact with a 3rd party site regarding integratrion of FIT2 files. they provided a piece of information which maybe explains why subSport SUB_SPORT_LAP_SWIMMING is not working properly.
    3rd party sites expect, that lap swimming fit files contain length messages, instead of record messages.
    current CIQ implementation does not allow developers to send length messages. maybe the fit file is empty, because the app didnt send any length messages (it has no way to send them).

    are there plans to allow us the send length messages?
    otherwise it does not make sense at all to have lap swimming in the sub sport enumerator. you should remove it, it will only cause problems.
  • Length messages

    hi,
    i was in contact with a 3rd party site regarding integratrion of FIT2 files. they provided a piece of information which maybe explains why subSport SUB_SPORT_LAP_SWIMMING is not working properly.
    3rd party sites expect, that lap swimming fit files contain length messages, instead of record messages.
    current CIQ implementation does not allow developers to send length messages. maybe the fit file is empty, because the app didnt send any length messages (it has no way to send them).

    are there plans to allow us the send length messages?
    otherwise it does not make sense at all to have lap swimming in the sub sport enumerator. you should remove it, it will only cause problems.


    Hi,
    i have realized that i need to send length messages for stroke data, if i want 3rd party sites to display them. All nativeIds for stroke data is part of length messages.

    i tried to send them by setting the proper index when creating the filed. The proper number can be found in profiles.xlsx on fitsdk.
    unfortunately the simulator crashes. I havent tested in watch , but i guess it will be the same.
    it should be really easy for you to support it, becaus it is actually same as a record Message, but with a different id.
    can you please open a ticket for this?

    thanks