different FITcontributor issues on Connect(Web) and Android App

The custom developer FIT-field issues have already decreased a lot, but there are several issues left regarding FIT recordings...

I also noticed that the ordering seems kind of random, what seemed to help in the past for me is to change the color code in order to force a new order and/or change the amount of fit fields (temporarily reduce it to 1 and then add more back...) (maybe custom fit fields are subjected to some sort of caching ?).

I couldn't find a mention of the String recordings issue in the bug reports forum so that's potentially a new issue.

(For future bug reports it helps to include a small code sample to reproduce the issue - even in cases like these where the code is straightforward to produce).

It's likely that it's a bug, but what you can already to verify if you did the programming right is:
* use the monkeygraph tool to visualize the fit file on your pc
* import the fit file in another tool that can read fit files (eg SportTracks Desktop + Garmin Fit Devices plugin).

Thanks for your reply!
With Monkeygraph I have the third different result now: the order is correct, the strings are correct, but the Value of my numeric object is now: "#VALUE?". But this Value is correct on the Androidapp and on connect. Very strange.

but the Value of my numeric object is now: "#VALUE?". But this Value is correct on the Androidapp and on connect. Very strange.

I found out, that this was because of the precision was set for the numeric value. I did that, bcecause the Programmes Guide says: "0 for integer, 1 for one decimal point, 2 for two decimal points. Without this attribute the default is no rounding". So I set it to zero, but after removing the option, the Value is corrrect in Monkeygraph, so everything is as expected in monkeygraph now. The issues in the app and connect remain.

.