App properties - lost on settings change - issue on simulator and real devices

Still as per the thread here from 2 years ago in 2016: https://forums.garmin.com/forum/deve...ettings-change

Steps to reproduce
1. Create simple data field
2. Add property called 'usereditable' along with a setting in properties.xml
3. Add property only called 'noneditable' in properties.xml
4. run app and change the settings of 'usereditable'
5 save settings

Effect: The settings file is rebuilt on the device to only include the 'editable'
(I've verified this with actual devices opening the settings file as a hex file)

It says here https://developer.garmin.com/connect...urce-compiler/

"

Properties are constant values defined at build time and included in the executable that are useful for product-specific values that shouldn’t be defined in code. Properties may also define the default Settings values."

But this doesn't seem to work. It seems like a major bug if you define non user-editable required values but they get erased when settings are saved

Former Member over 8 years ago

djhawley

Can you tell us more about the app, the device and device firmware you are experiencing this with?
Is this something we can download to replicate or do you have a code snippet we can try to reproduce this issue with?

Thanks,
Kamau

djhawley over 8 years ago

I've attached a sample project which just displays two properties in the datafield. One editable in settings, one non editable.

If you run the project it reports the default values from properties.xml

If you edit the settings you see the editable one change, and the non-editable one changes to null.
(if you open the updated settings file you see this is because the non-editable property has been removed)

In the simulator this seems to resolve with a restart of the simulator most of the time. But on actual devices (forerunner 735xt) i've seen this problem persist after restarting the device and updates of the data field

Former Member over 8 years ago

djhawley

Perfect, thank you! we've created a ticket for this bug.

Thanks,
Kamau

Former Member over 8 years ago

this bug occured about half year.

Former Member over 8 years ago

I wanted to give a little FYI that we have this prioritized and reproducible. I'm hoping that we will see a fix in place soon.

Thanks,
- Coleman