Red X screen/crash on Vivoactive

I've been getting user reports of getting a black screen with a red X when they start my app (dwMap) on certain Vivoactive watches.

Here's a screenshot of it, send in by a user:

Searching the forum it sounds like it's been seen with other apps on the Vivoactive. I cannot reproduce it on mine (and the Vivoactive is my main test watch). Users say they have the latest (3.20) firmware.

Any ideas?
  • This is a hard crash. I've not seen the "X" since maybe the 2.60 version of the FW. If you can, have one of the users send you the "err_log.txt" (it in the root directory on tha va). You can then pass it on to the garmin folks. But look at it first, as there is info on which version of FW they are actually running.

    On the va for example, with version 2.50 (or older) FW, simply using "phoneConnected" without checking for it with "has" would result in a crash like this. I'd guess they aren't really running 3.20, but something older...
  • Former Member
    Former Member over 9 years ago
    I've been getting user reports of getting a black screen with a red X when they start my app (dwMap) on certain Vivoactive watches.

    Here's a screenshot of it, send in by a user:

    Searching the forum it sounds like it's been seen with other apps on the Vivoactive. I cannot reproduce it on mine (and the Vivoactive is my main test watch). Users say they have the latest (3.20) firmware.

    Any ideas?


    If a user is seeing this screen, and they believe they have the latest firmware, they are mistaken.

    This is an early place holder for the App crash screen that accidentally slipped out in the first 1 or 2 VivoActive firmware revisions that supported ConnectIQ (Approximately version 2.40 I believe).

    Unfortunately there were also several device issues that caused app crashes in these early versions, so it is likely your app isn't doing anything wrong to cause this crash.

    These users can check their version under Settings->System->About. If they are experiencing issues updating their software, they should contact Garmin Product Support.
  • If a user is seeing this screen, and they believe they have the latest firmware, they are mistaken.


    Excellent info, thanks, I will have the users in question recheck their firmware versions.