Under Review
over 1 year ago

Wrong value sometimes read for when no corresponding definition exists

In supporting multiple devices, sometimes I have a <property> defined with a default value, but the <setting> is only defined for certain watch models.  I expect that for watch models where the <setting> is not defined, the default value is read by Application.Properties.getValue(key);

However sometimes this does not seem to be happening properly, at least for boolean properties I have noticed this happening on more than 2 watch models.  Either the default value is not read or read incorrectly, or something is corrupting the property value.
I have noticed this just recently on the 
  • Device Name: Forerunner 955 Solar
  • Firmware Version: 13.22

but it has happened on other watch models.