The CIQ 3.0.1 SDK has been released!

If you've not been using the 3.0.0 betas, one thing you may run into is

• New automatic symbol checking (ASC) checks your code for mis-typed symbols at compile time, but keeps the dynamic functionality of Monkey C
  

You may get compile errors on things that compiled fine with 2.4.x. BUT THAT IS A GOOD THING! Catching typos in rarely used code paths that would have resulted in "IQ!" crashes in the past for example!

If you run into any 'head scratchers", post about it and others can help!

Very nice, thanks for the information!

What about the notification stuff that was added in CIQ 3.0? I have read somewhere that this will not be available for all developers but only for some specific apps and that developers can ask permission for that. Any news about how this works?

Bye

Guys… is something wrong with CIQ 3.0.1?

I'm testing my app in debug environment and tried to switch to Edge 1030, Bontrager - immediately got error :

Symbol Not Found Error
on line with: App.getApp().getProperty(…

While compiling on Edge 1030 does not produce such error


Thanks!

I'm seeing the same thing with one of my widgets in a normal run configuration. With the 1030 Bontrager, I get

"Could not find symbol getProperty"

Other targets run fine.
Update: I posted a bug report
https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/1390462-getproperty-throws-compiler-error-on-e1030-bontrager-only-3-0-1-sdk

I would like to experiment with 3.01 when i have time but i absolutely need to retain ability to build under 2.x. If i load the new eclipse plug in, can i still select to use the older 2.x SDK and build as before?

One thing to consider is even though the SDK is 3.0.1, it still builds for CIQ1 and CIQ2 devices (backwards compatible), and on top of that, it's got some fixes/new features that weren't backported to the 2.4.x SDKs.

I'd just move to the 3.0.1 SDK and leave 2.4.x SDKs behind (that's what I'm doing). Any new features or devices coming will be in the 3.0.x SDKs.

As far as the new plugin with a 2.4.x SDK, I think that should work fine (I was doing that and switching back to 2.4.x to build .iq files while 3.0.0 was in beta), but I don't think you'll need to worry about it. Just move to 3.0.1 for everything.

if i recall the 3.x does not support edge 520. if that remains the case then i cannot use it for some applications that need 520 support - a lot of people have that device. I need to be able to build 2.x to support them.

The 3.0.1 SDK supports the 520 just fine. (Along with all other CIQ devices.)

The thing you are thinking is the VM on the device. The 520 isn't going to a CIQ3 VM on the device, but the 3.01 SDK still builds for it just fine.

The SDK version doesn't define which series it can build for. The 2.x.x SDKs built for CIQ1 and CIQ2 devices, and this SDK builds for CIQ1, CIQ2, and CIQ3 devices.

Transition from 2.49 to 3.01 is relatively painless, only problem is that some datafields where max memory usage stayed under 28,7kB now crash because of "out of memory". :(