SDK 1.2.11 and large number of reported problems

I updated my BigTime watchface to build against 1.2.11. Since then I've received many reports from users of problems. I never had these issues before. Any suggestions? Here are some of the reported issues:

You probably know by now but your watch face has stopped working on the Forerunner 235 after the last FW update from Garmin.
---
it doesn't work with v7.10, last update, please fix it - 920xt
---
When choosing Bigtime as the watch face 920xt returns to the default digital watch. Other Connect IQ watch faces turn up/work. I have tried to remove and reinstall without success. Worked until the update 18 July.
---
Please tell me. BIGTIME no longer work in 920XTJ. Other applications are operating. The Garmin is installed. It appears to have been ignored by Garmin.
---
I have just to underline this issue: the wonderful Bigtime watch face doesn't work any more. It has happened to me today, after the automatic download of the last version of Vivoactive software. Please fix the bug, because the Bigtime face is much more impressive than the original one. - Vivo Active
---
New version don't work. International: Italian
---
Hi! After updating to the latest firmware on my Vivoactive I can't get the BigTime watch face activated. It downloads and shows as an option on the watch face, but when it does not activate when selected. Any ideas on how to resolve - Vivo active 3.80
---
Hi, please help me out on this, after updating my forerunner BigTime just won't show. I have restarted the watch and been in Garmin Express and changes some settings in BigTime saved and updated the watch. Please help, I miss my BigTime sooo much. - Forerunner 4.70
---
After my last sun, BigTime is no longer selectable as a watch face. Or, I should say, I can try to select it but it doesn't take and I revert to the analog face. ActiFace is selectable and works. - Fenix3 HR 3.80

jim_m_58 over 8 years ago

What are you seeing in the ciq_log.txt file from the watches?

Are you trying to use new features from 1.3.x/2.1.x that aren't available on watches with a 1.2.x VM?

Are you sending out sideloads built with 1.2.11 where people have one of the beta FW releases with 1.3.x or 2.1.x VMs? (doing this will cause a "signing error". See the sticky on app signing at the top of the forum)

ruperthawkes over 8 years ago

I dont think I'm using features from 1.3.x/2.1.x as I'm using 1.2.11

I don't think I'm side loading, I'm building by using the app export wizard thingy and uploading the the app store.

jim_m_58 over 8 years ago

Ok, things built with a 1.2.x SDK should work with devices that 2.1.x 1.3.x VM if downloaded from the store.

Back to the first question - what's in the ciq_log.txt files from watches having problems?

Oh - one other thing. Are you trying to display the heart rate? There was a problem with at least some of the beta FW when it came to ActMon.getHeartRateHistory() when it came to invalid readings. Instead of being "INVALID_HEARTRATE", a null was returned.... And the call is only available for devices with a WHRM to begin with..

ruperthawkes over 8 years ago

I do allow show heart rate as an option. Should I test to see if it's possible to call get heart rate first? How can I prevent users from selecting it if it's not supported?

jim_m_58 over 8 years ago

You're code would have to specifically go out and get the HR, so that's not it.

1.2.11 was a pretty minor update. Which get's back to - what is in the ciq_log.txt on watches?