Issues upgrading an App

Former Member over 9 years ago

Hi,
every time I upgrade WatchOut! on the watch from Garmin Store I have to reboot the watch in order to see it upgraded.

WatchOut! app has a menu with an About function that reads a resource string with version info.
Unless a reboot I read the previous resource string version value.

This upgrade behaviour sometimes leads to others anomalies.

Are you experiencing something similar?

I have been seeing this behaviour since I upgraded my F3 firmware to 6.50 or released WatchOut! on latest Garmin ConnectIQ 1.2.2 or I started to use watch setting.
Don't know which one is the problem.

Nikeow over 9 years ago

sounds like my problem too.
See my thread.

Former Member over 9 years ago

sounds like my problem too.
See my thread.

I will look at the watch file system and let you know.
In my case a reboot fix the problem.

lcj2 over 9 years ago

I would guess it is the F3 firmware. Many of us have reported issues with CIQ after the upgrade to F3 FW 6.50 or the betas post 6.50. The running list so far is:

- loss of sensors after first app run (HR specifically)
- loss of ANT+ use after first app run
- multi sport FW take over in specific activity session use cases
- almost every issue on the FW is corrected on reboot for the next app run then breaks again

I have found that my apps regardless of versions continue to work perfectly on other devices but are beginning to have more and more problems on the F3.

Former Member over 9 years ago

well, I went to the watch file system and found my app under \GARMIN\APPS and its data store under \GARMIN\APPS\DATA.
I then upgraded it, went back to the file system and found the old and the newer.
I launched it and the watch picked up the latest and everything ran ok.
Finally I checked again the file system and I found just the newer app.

so basically I couldn't replicate the problem this time.

Brandon.ConnectIQ over 9 years ago

I'm meeting with one of the F3 quality staff today to talk some of these items over. I'm not sure how many they're familiar with at this point, but I know I've reported a couple of the items lcj2 mentioned above. We've already had a handful of internal, development releases that have addressed some of these problems, so I know they're getting fixed. I just want to make sure that we have everything covered before the next public release.