Complete
over 4 years ago

SDK 3.2 Application Settings no longer in synch with actual simulator settings

To replicate:

1. Start an app...

2. Use Application.getApp().setProperty(key,value); to set a property

3. Use Ctrl + M to verify setting is stored in ApplicationProperties

4. Restart the app 

5. Use Ctrl + M to verify setting is still stored in ApplicationProperties

6. Start Application Settings

ACTUAL BEHAVIOUR

7. Note that entire settings form has been reset to default values. It is not referring to current application properties at all.

EXPECTED BEHAVIOUR. 

 7. Application Settings should open with current values of application properties

9635560
Parents
  • over 5 years ago

    I'm not following this at all.  What target?  

    Did you renamed the app?  If so, and it's still got the same manifest ID, you may want to clear things out of the sim's temporary directory as there can be some confusion with the name of the .set file

Comment
  • over 5 years ago

    I'm not following this at all.  What target?  

    Did you renamed the app?  If so, and it's still got the same manifest ID, you may want to clear things out of the sim's temporary directory as there can be some confusion with the name of the .set file

Children
  • over 5 years ago in reply to 9635560

    PS: I don't know whether the change is linked to this which, while I have a workaround so I haven't listed it as a bug, is still an irritating change to SDK behaviour that makes testing more painful than it used to be: https://forums.garmin.com/developer/connect-iq/f/discussion/236702/device-specific-settings-is-this-a-change-or-is-it-a-bug-if-the-former-how-do-i

  • over 5 years ago in reply to jim_m_58

    I have just done that - deleted the entire of %TMP%

    This is what I see:

    The top box is the "Ctrl + M" I did before opening settings.

    The grey form is what I see in "Application Settings Editor".

    Something has changed.

    G

  • over 5 years ago in reply to 9635560

    Is it only one app?  What you're describing consistently works for me,

    I'd still try deleting the sim's temp directory and see if it still happens

  • over 5 years ago in reply to jim_m_58

    Let's save you have a projected called Ver1, and you've be runnint it in the sim.

    In the sim's directory under apps, there will be Ver1.prg and under apps/setting, Ver1.set

    If you rename Ver1 to be Ver2, or copy Ver1 and have a Ver2, and then run that, under apps you'll have Ver1.prg and Ver2.prg, and under apps/settings, Ver1.set and Ver2.set.

    But here's the twist.  The prg files both have the same manifest ID.What can happen is that Ver1.set and Ver2.set get confused, as far as what's used by the sim and what's used by the app settings editor.

  • over 5 years ago in reply to jim_m_58

    Jim, none of those are relevant! None of those are changing. I am simply testing a single app using a single manifest on any single device without changing any filenames or even files.

    This is the workflow that used to work:

    1. Start app.

    2. Make changes to app.

    3. App stores those changes on exit or whatever.

    4. Relaunch app.

    5. Launch settings editor - settings displayed match the settings in the app, these also match the settings you see if you do Ctrl+M and inspect ApplicationProperties

    But what is NOW happening is this:

    Application settings ignores any and all previously stored changes and simply reloads with all values reset to the default values in Properties.xml.

    This may or may not be tied to another change I noted in a thread earlier this week where I could not view settings for different devices without disabling the "rebuild". However, for this specific bug, the "rebuild" flag makes no difference... application settings editor currently ignores all saved settings no matter what you do, despite the application itself receiving and using those settings.