SDK 1.1.1 Release Available!

We recently released version 1.1.1 of the Connect IQ SDK yesterday, and it's available for download:

http://developer.garmin.com/connect-iq/sdk/

You may also download through the Connect IQ SDK Manager in Eclipse, by clicking the Help menu, selecting Open SDK Manager, and then clicking the Download button for Connect IQ SDK 1.1.1 released April 20, 2015.

v1.1.1

Do not support swipe up/down in simulator to match current device behavior
Fix simulator onHold() event reporting incorrect coordinates
Fix corrupted 1-bit palette bitmap display
Fix size/alignment of round watch display region to prevent clipping
Add Japanese Gregorian translation
Add English support to APAC devices
Add Thai language support
Disable "Not Set" language option for running applications
Allow applications to pass an input delegate into Ui.pushView() when creating a progress bar. The progress bar should only be able to be popped if the developer specifies an input delegate when pushing the dialogue. If null is passed then the progress bar will remain on-screen regardless of input.
The simulator now kills an application when pressing back on the base page
When adding a Duration to a Moment, Duration.value() will now return a long to avoid floating point number precision loss
Fix several stability issues with the geometry iterator
info.StartLocation now correctly initializes to null on devices
getSystemStats() now returns the correct used/free/total memory amounts
The FIT recording session will now be saved when a new session is created, or if the application is closed
The dst field in Toybox::System::ClockTime is now correctly populated
Activity monitoring history now uses the UNIX time epoch
Calling Toybox:System::println(null) now correctly prints "null"
Fix issue where Toybox::Application::deleteProperty() would not always delete a specified property depending on call order with setProperty()
Changing the content of a property ID from a string to a number using Toybox::Application::setProperty() will no longer result in a crash
Using a sub sport greater than SUB_SPORT_FLEXIBILITY_TRAINING should no longer give an unexpected type error
Fix several device crashes and memory leaks under various circumstances
Various other minor bug fixes and documentation updates

Known Issues:

Exceptions are not working correctly

-The Connect IQ Team

Former Member over 10 years ago

Good stuff.

Do not support swipe up/down in simulator to match current device behavior

Would trying to call these functions be likely to cause a crash on a device?

jim_m_58 over 10 years ago

Bummer - it seems doing more than 10 makeJsonRequests() still kills the simulator - but now it just goes away with no windows dialog that it crashed....

travis.vitek over 10 years ago

Is it crashing if you make 1 request, wait for 1 response, and repeat 10 times, or are you just creating 10 requests without reaping the results?

jim_m_58 over 10 years ago

Any 10 makeJsonRequests. Even if you just run the same thing 10 times. It's an issue I first reported a month or so ago. As long as you make the call, crash after 10! Kyle acked the error and said it would be fixed, and I'd hoped this would be the fix!

Nikeow over 10 years ago

anyone can download the SDK? I keep getting DNS errors or server not found.

Former Member over 10 years ago

Good stuff.

Would trying to call these functions be likely to cause a crash on a device?

These are callback methods in the behavior delegate, so you wouldn't be calling them. The change refers specifically to the VivoActive (and square_watch). The VivoActive does not send swipe up and swipe down events, but the simulator previously did. If you implement onSwipe for your app, it will never receive the up and down directions.

Former Member over 10 years ago

These are callback methods in the behavior delegate, so you wouldn't be calling them. The change refers specifically to the VivoActive (and square_watch). The VivoActive does not send swipe up and swipe down events, but the simulator previously did. If you implement onSwipe for your app, it will never receive the up and down directions.

Ok, maybe I didn't phrase it right. I'm getting reports of my app crashing the Vivo, and my swipe handler first checked for Ui.SWIPE_UP, then Ui.SWIPE_DOWN. So I guess I should have said could checking for these events possibly cause an error. I always thought it unlikely, but I'm grabbing at straws.

Petr.Koula over 10 years ago

I can see only version 1.1.0. Was it rolled back?

Former Member over 10 years ago

Ok, maybe I didn't phrase it right. I'm getting reports of my app crashing the Vivo, and my swipe handler first checked for Ui.SWIPE_UP, then Ui.SWIPE_DOWN. So I guess I should have said could checking for these events possibly cause an error. I always thought it unlikely, but I'm grabbing at straws.

I don't think so. Ui.SWIPE_UP and Ui.SWIPE_DOWN should still be defined in the SDK, the VivoActive (and now the VivoActive in the simulator) will never send those events.

The current released version of the VivoActive software is missing a number of ConnectIQ bug fixes that are in the 920XT software, so I suspect something there is the source of the crashes your users are seeing.

Former Member over 10 years ago

I can see only version 1.1.0. Was it rolled back?

Something isn't quite updated with the download links yet. I don't totally understand the details, but you should see it soon.