Acknowledged
CIQQA-3716

SDK 8.4.0 Code does not get updated after pushing a new update to the store

After compiling with 8.4.0 on Linux or Mac (I haven't tested on Windows) and pushing to the store, old code stays active and doesn't seem to be rolled out. However, changed settings ARE rolled out.
Compiling it again with 8.3.0 and pushing it to the store does work as expected


Expected behavior:
Code changes and changes in the settings files will be deployed after pushing it to the store

What happens instead:
Only settings are updated, the old code stays as is

To reproduce:
- Create a basic watchface and make it display "Hello world", add a setting "Hello World" compile with 8.3.0 and push to the store.
- Change "Hello world" to "Hello universe"
- Compile with 8.4.0 and push to the store again
- Wait like 30 minutes for it to be rolled out, Load on your watch, restart the watch to make sure it gets loaded, and it will display "Hello World" on the watchface, but "Hello universe" in the settings.

- Compile again with 8.3.0 and push it to the store, load it on your watch, restart your watch (...) and now it works as expected

- It makes no difference if the app was installed on the watch before or if it is a fresh install.


Workaround:
Compile with 8.3.0 and it works as expected.

GreenBlack
Parents
  • in reply to flocsy🤠

    b1 was happening before as well. Users see the new settings, but needed to restart their watch to load in the new code.

    It seems A1 is the case. I updated a test watchface about 28 hours ago. The settings changed instantly, but 24 hours later the code still wasnt updated. Even a fresh install on a fresh device still showed the old code, so its not like it was before, where users that had the old version installed kept seeing the old code until the watch was restarted (indicating the issue on the watch itself). A fresh install indicates the code isn't being updated in the store itself.

Comment
  • in reply to flocsy🤠

    b1 was happening before as well. Users see the new settings, but needed to restart their watch to load in the new code.

    It seems A1 is the case. I updated a test watchface about 28 hours ago. The settings changed instantly, but 24 hours later the code still wasnt updated. Even a fresh install on a fresh device still showed the old code, so its not like it was before, where users that had the old version installed kept seeing the old code until the watch was restarted (indicating the issue on the watch itself). A fresh install indicates the code isn't being updated in the store itself.

Children
No Data
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries