Problem: developer creates a data field that works perfectly alone or with even some other CIQ data fields, but can crash for reasons caused by other developers' data fields, because of the limitations of number of fit fields per field type per activity or on the total number of bytes all the fields (per type) can have.
Unfortunately neither of the 2 errors I see in ERA (that according to my understanding are caused by either having more than 16 fit fields of the same type => System Error, or by having too many bytes of the fit fields' size alltogether => Out Of Memory Error) can be caught with try/catch :(
I know this came up a few times in the past, and I know most developers think that Garmin should do something with this, but until that, what do you recommend to do? I could think of not very useful things like:
- ignore the System error, Out of memory error in ERA when it's from the function that creates the fit fields => crashes => bad user experience
- add some explanation about how other fields added to the same activity can cause my data field to crash => not the best user experience (most won't even read)
And then one that can be a bit more useful:
- add settings for each of my fit fields to be able to enable/disable them separately, and by that hopefully users with crash (and who read the description...) will be able to keep the more important fit fields while giving up on the less important => adds lot of code