Ticket Created
over 3 years ago

CIQSTORE-2960

new settings are not visible after downloading new version for couple of days

Why the settings are not visible after updating the application?

Even changes to the labels are not updated immediately - I had to wait 2 days to new settings.

Settings are handled online (device's settings is available from 3.2.0 cost code/memory).

- new app + new settings

- upload to store

- accepting new vesrion for downloading  - FROM THIS MOMENT NEW SETTINGS SHOULD BE READY

- users can download new app

- for couple of days users cant' use new settings or they see old labels...

It means users have to use default values hardcoded (if developer doesn't forget to handle it and it's additional waste of time/memory because default values should be always returned as defined in properties.xml but they don't or rather they are after couple of days).

_psx_
Parents
  • over 3 years ago

    "- API is one and applications on watch many - so  each takes memory

    - loading bigger app consumes more energy"

    Garmin implemented symbols/has and exclude annotations.

    We can agree that it's insufficient for maximum memory savings, but I can understand why they didn't want to include line-by-line conditional compilation with #ifdef. There are a lot of things in Monkey C that waste memory, besides the lack of a built-in preprocessor.

    Given that we can use a preprocessor on our own (or write the same code over and over again, with exclude annotations), I would prefer that they revisit some design decisions, like the app settings strings fiasco.

Comment
  • over 3 years ago

    "- API is one and applications on watch many - so  each takes memory

    - loading bigger app consumes more energy"

    Garmin implemented symbols/has and exclude annotations.

    We can agree that it's insufficient for maximum memory savings, but I can understand why they didn't want to include line-by-line conditional compilation with #ifdef. There are a lot of things in Monkey C that waste memory, besides the lack of a built-in preprocessor.

    Given that we can use a preprocessor on our own (or write the same code over and over again, with exclude annotations), I would prefer that they revisit some design decisions, like the app settings strings fiasco.

Children
No Data