Watch face support for Vivoactive 3

I have downloaded the latest 2.3.4 SDK and included support in my watch face for the new Vivoactive 3. Everything seems to test fine in the simulator however I have users reporting fundamental things do not work. When notifications arrive the screen blanks out and just displays the Garmin 'blue triangle'. If they long press on the face the options appear but when the select watch faces and scroll to my watch face nothing appear.

There is nothing in the CIQ_LOG.TXT file so it seems like there is something I am not returning from the onUpdate or onLayout functions that is expected on this device ? or some new function call for single button devices I am not supporting ? I have read what I think is the available documentation on supporting Vivoactive 3 and cannot find anything. Can anyone point me at some other doco, topics or samples in this area ?
Thanks

jim_m_58 over 8 years ago

The blue triangle indicates the device crashed, and it's not a CIQ crash. Look for err_log.txt on the watch (in the garmin folder). Sounds like a firmware problem to me.

What version of firmware is on the watch?

Beeso27 over 8 years ago

All 3 users who have contacted me so far have been running 2.4 firmware.

Thanks

jim_m_58 over 8 years ago

See if you can get an err_log and forward it to garmin. BTW, the last digit of the FW number is important if there are public betas. (the fenix devices are big on that) A zero is a production release, and non zero is a beta , so it's really 2.40 and not 2.4 :)

Beeso27 over 8 years ago

Jim, I managed to get an error log file from a user for you. Thanks

Beeso27 over 8 years ago

Jim, any update on this or should I post that error log to another forum for the firmware team to respond ? Thanks

jim_m_58 over 8 years ago

Maybe do a CIQ error report (in that forum) to make sure Coleman sees it. 2.50 is out now - do you know if the problem still occurs?

Beeso27 over 8 years ago

Thanks to Garmin they were able to identify that code in the onHide() function that was causing a crash. Whilst it is a problem on the device I was able to code around it in my application so I could get a supported version of the application in the store. Thanks.

jim_m_58 over 8 years ago

Could you post about what the actual problem you had in onHide was, so others can watch out for it?

Former Member over 8 years ago

Calling Ui.RequestUpdate() from the onHide() method currently triggers this bug on VVA3. A fix for this issue should be made in the device firmware in one of the next releases.

jim_m_58 over 8 years ago

Thanks Brian!