FitContributor and Strings

Hi,

I'ved used FitContributor with numerical data and MESG_TYPE_RECORD before successfully, however I am struggling using string data with MESG_TYPE_SESSION.

The App (not Data Field) correctly writes to the Fit File and Garmin Connect, but always shows '0' in the field. Now I am sharing the 256 bytes over two values if that's important. But both are currently showing '0'

The code is:

_recordingFieldScore = _recordingSession.createField("Score", 0, FitContributor.DATA_TYPE_STRING, { :mesgType => FitContributor.MESG_TYPE_SESSION, :units => "Score", :count => 6 });
        _recordingFieldHistory = _recordingSession.createField("History", 1, FitContributor.DATA_TYPE_STRING, { :mesgType => FitContributor.MESG_TYPE_SESSION, :units => "History", :count => 250 });

Any ideas?

Cheers
Chris

danielp27 over 7 years ago

This is a very old, known issue.
strings are shown in android app, but are shown as 0 in the browser.

chrishares over 7 years ago

Thanks. I’ve checked, and I just get ? in the iOS App. Any ideas if this is going to be fixed?

danielp27 over 7 years ago

If it will ever be fixed, should be answered by garmin guys. It is reported since at least one year ago.
I am pretty sure there was a ticket for this.

Coleman.Apps over 7 years ago

Hello,

There are multiple tickets here over several platforms. The one that's been sitting for a long time is the one regarding the Garmin Connect website itself. Because of the gravity of making fixes in that ecosystem, it takes a long time to get issues prioritized and implemented. I know that these issues have been up prioritized and we have had some movement on those, but I can't give any real status updates on things regarding the Web interface. The Garmin Connect Mobile iOS issue has been reported. This is fairly recent regression to an older bug. The timelines on the mobile platforms are generally not as lengthy as the web, though they do tend to be longer than items we can address within our team (SDK, Simulator, documentation, etc). So the short answer to the question of "if" these will be fixed is "yes", but it's the timing that is the difficult thing to pinpoint.

Thanks,
- Coleman