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 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.

Comment
  • 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.

Children