Ticket Created
over 4 years ago

RENU-12503

Express is corrupting Settings

When I use Express to change my app's settings, the app crashes next time it runs when it calls Properties.setValue().

CIQ_LOG shows "Key does not exist in Application Properties"

If I then use Connect to view / save settings, with or without any changes to settings, this problem goes away.

If I once again use Express to save settings, the app crashes on startup once again.

Somehow Express is corrupting settings, and Connect is correcting the problem.

More info...

I can set all of my app settings in Express which allows easy cut / paste for my settings.

If I then run Connect and look at the settings, all of the settings are correct, so Express is in fact setting the correct values in the settings fields, yet it leaves the settings file in a state that causes a crash.

This is happening on my Forerunner 245 Music, and my Vivoactive HR.

More info...

The settings fields that were causing the problem were alphanumeric fields that were defined with readonly = true.

Changing readonly to false stops the problem, but leaves me without being able to set these fields as read only.

Conclusion...

Express is mishandling read only alphanumeric fields (maybe all read only fields ??) in some way that results in a runtime exception "Key does not exist in Application Properties",

when, in fact, the key does exist.

I hope you will fix this.

Jeff
  • over 4 years ago in reply to Brad.ConnectIQ

    My current version is 7.5.0.0

    I avoid using Express at this point because when I update my app using Express it removes my app from my watch and with the app, it removes all of my settings.

    That behavior is on top of corrupting the settings if I make changes.

    I've changed my settings definitions to remove readonly. That "fixed" the settings corruption problem but Express still removes the app and I'm not sure that I've characterized what circumstances cause it to remove the app other than attempting to load an updated build.

    Since this doesn't seem to be a broad general problem between Express and the Fr 245 M, I suspect that it is relate to the fact that I'm loading an unreleased app that's in development.

    I'm hesitant to try using Express again since it's such a time burner when it removes the app and all of it's settings.

    It would be nice if this doesn't get classified as "not reproducible" and closed.

    It's an ongoing problem.

  • over 4 years ago

    What version of Express were you using that you saw this issue on?