CIQ 3.2 - Wow!

Just installed 3.2 (see https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-2-now-available),

and in looking at the change log in the SDK README file, a bunch of new features!

Time to start trying stuff!

Top Replies

PlayItLoud over 4 years ago +4
Same code. One running Connect IQ 3.2... Guess which one

Just added this at the top of my onUpdate(dc) method:
```
if(dc has :setAntiAlias) {
    dc.setAntiAlias(true);
}
```
xuxumatu over 4 years ago +1

ERA is no starting
PlayItLoud over 4 years ago +1

NICE! Watch faces and data fields can now have user-configurable on-device settings with settings views.

All Replies

jim_m_58 over 4 years ago in reply to Kurev

Sounds like a bug in the sim, as menu2 should always use the full screen. Do a bug report and include the target device, and the layout you are using. (2 field, 3 field, etc). And maybe the code for your DF or a simple way to reproduce this.

André Zunido over 4 years ago in reply to jim_m_58

Hi Jim, do you know how does one check if a bug has been reported, I also have this issue: clicking "Start ERA" entry -> nothing happens. macOS Catalina (10.15.6)

jim_m_58 over 4 years ago in reply to André Zunido

Look in the CIQ bug reports. Sorting by date would help.

Kurev over 4 years ago in reply to André Zunido

André Zunido said:
Hi Jim, do you know how does one check if a bug has been reported, I also have this issue: clicking "Start ERA" entry -> nothing happens. macOS Catalina (10.15.6)

Here is workaround from devs, at least they are well aware:

https://forums.garmin.com/developer/connect-iq/f/discussion/236055/workaround-for-issues-launching-sdk-tools-with-3-2-1-connectiq-plugin

Nik over 4 years ago

"You're going to want to read this, because we changed everything"

What every developer wants to hear! ;-)

Wonder if they are going to list those devices that will never support 3.2?

jim_m_58 over 4 years ago in reply to Nik

There's a list of what the SDK currently does, and there are others getting it - like the 945 that got it the day before the SDK was released, so the list of devices will be changing. If you mean long term, I doubt it will all be short term - like this week.

And you also need to think about ROW/WW vs APAC.

All I can say, is right now "has" is your friend.

Kurev over 4 years ago

I have app which among other features would be using BLE, but because there is this bug, I have disabled it:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/ble-related-device-crash

I haven't been able to verify yet, but I hope this change in 3.2 might fix it:

"Fix a device crash that can occur when an app using BLE shuts down."

If it does fix it, I'd like to enable the BLE feature on 3.2 devices, but leave it off on older versions. Any ideas how to go about it? There is no direct 'has' check I could us in this case, I suppose I could hack it by using 'has' on some totally unrelated new feature introduced on 3.2., but this feels a bit crappy way. Is there other way of checking the sdk version runtime, or some monkey.jungle tricks?

jim_m_58 over 4 years ago in reply to Kurev

Actually, it's not that hard. In your code you can check Sys.getDeviceSettings().monkeyVersion to see if it's 3.2 or greater.

I'm already doing that to check if persisted scan results can be used.

When are you seeing the crash and on what devices? I've not seen a crash involving BLE in a long time.

Kurev over 4 years ago in reply to jim_m_58

Oh awesome, I just read the API doc through couple of times, but somehow managed to miss this totally. Just saw firmware version etc. Thanks a lot, this will be perfect :)

I got few resets just yesterday on Edge 530, when playing with BLE stuff. Both cases which I describe in that error report.

sabeard over 4 years ago in reply to Kurev

The Edge 530 FW does not yet support CIQ 3.2 despite the new release that just came out last week. Best advice is try it out, but you may have to wait for one more FW release.