Problem with settings in GarminExpress with length of alphanumeric

My app had (before) a limit in number of characters in strings, in the settings
But in GarminExpress, this limit cause a problem, impossible to modify the strings. It said a problem of length
In Gramin Connect Mobile, it was OK

Then I have deleted this limit in my settings
But still have this message in Garmin Express

Cannot modify my waypoints in Garmin Express

Someone know the solution ?

Thanks

dududu13 over 7 years ago

Up
Still had the problem and cannot find a solution
My users can't modify their waypoints with Garmin Express cause of the error message
Thanks

Brandon.ConnectIQ over 7 years ago

Can you provide an example (e.g. how long are the strings you're working with?) and perhaps some code that demonstrates the problem? I'd like to try to reproduce this, but I don't have enough information yet.

riedid74 over 7 years ago

Hi dudu13

With garmin express the maximum length in a field is 800 chars.

You must create several fields and after make a concatenate of several fields.

field1='800 chars'
field2='800 chars'
field3='800 chars'
field4='800 chars'

FieldAll=field1+field2+field3+field4 ;

Didier

easuvorov over 7 years ago

Currently I'm developing an app, which relies on setting string generated by external web app. This is a data field, therefore it's not possible to use makeWebRequest and the Garmin Express/Mobile is the only way to send settings to the app. I do not use "maxLength" attribute in my settings definition. In simulator I am able to transfer strings with sizes of around 600 symbols without any problems as a single value, but when I use actual version of Garmin Express, then strings are cut at 256 symbol even if I paste larger strings. For obvious reasons I cannot test this behavior via Garmin Mobile as the app is still in development and pushed to the store with "DO NOT APPROVE" label.

Can someone, please, shed some light on this behavior as there's no mention of string setting length limitations in documentation and previous posts in this thread state that there's a 800 symbols limit to the string setting (and this was an assumption I based my original implementation on). Of course there's always a workaround of adding new properties/settings and using a concatenated value of those, but my data field is very functionality packed therefore even addition of three settings gives me very noticeable 200 byte memory consumption impact.

Thanks in advance for the detailed explanation.

Coleman.Apps over 7 years ago

Hello,

I've been able to reproduce this in part. I have opened a ticket to investigate the intended behavior and bring all the app settings platforms in line.

Thanks,
-Coleman