Complete
over 4 years ago

WERETECH-8010

Fixed

Vivoactive 3 firmware 6.90 cause watch faces to crash

Please check the newest firmware for issues that causes watch faces to crash.

e.g. https://apps.garmin.com/de-DE/apps/fc3f9b9f-add6-46cb-8e0b-9a2172a04c31

All vivoactive 3 users with the latest firmware are reporting the same affect, the watch face crashes directly. No start is possible.

No crash error logging is written into the log file of the watch.

The simulator of the SDK works perfectly with the watch face (3.0.12/3.1.4) and the last issues caused by the watch face was reported a year ago.

Thanks for support and please keep up testing your software.

The Magician

TheMagician
  • over 5 years ago in reply to Gertjan

    Hey guys, that makes no sense. We have to look at the final exported project. Only on the vivoactive 3 series the app/watch face doesn't work. All other supported devices are ok. I think Garmin have to look at the firmware or the compiler.

  • over 5 years ago in reply to ArtaudAntonin / Jiri Richter

    Was that also a silent crash with no entry in the logfile? I just loaded the crashing and non-crashing files in notepad+++ and saw no difference in line-endings

  • over 5 years ago in reply to Gertjan

    I remember having some weird issues about a year ago when some lines of my CIQ code (that was definitely not wrong) caused crashing but when I reentered them they didn't. Maybe it has something to do with line endings?

  • over 5 years ago in reply to TheMagician

    Knowing that two of mij widget crashed and having tried al solutions I could think of (including generating a new app-id), I first tried if an empty widget would work. I made a new project with another name in Eclipse and verified that id did not crash (and it didn't). Next i copied and pasted entire functions from the original sourcecode to the new project.(renamed classes as i went) and I copied resourcefiles.  In between I verified that it still worked (which by the way once did not when i copied an entire sourcefile to the new project). Of course I hoped that on the way I would discover which part of the source caused the crash, but none did.I ended up with a working widget that was almost identical to the original one. Only difference is I did not copy some unused resources and I used some other names for classes (and the entrypoint in the manifest). I did the same with another widget and got it working that way. Weird ... . Can't think of an explanation.

  • over 5 years ago in reply to Gertjan

    What means "reentering" the source code?

    Creating a new project, update the manifest file, adding the code line by line, etc.