iOS SDK returning a device UUID == 00000000-0000-0000-0000-000000000000

Former Member over 8 years ago

Hi team -
I'm in the middle of porting the iOS ExampleApp from Obj-C to Swift 3. I'll be happy to share that with you (Garmin) and the community once it's finished.

However I'm running into a problem that I'm hoping you can help me with.

After the GCM redirect, I receive the following URL as expected in the redirect back to the app:

pushmeter1233://device-select-resp?ciqApp=Connect&ciqBundle=com.garmin.connect.mobile&ciqScheme&ciqSdkVersion=10000&d0ID&d0Model=Edge%20520&d0Name=Edge%20520

Based on what I've seen from other threads on here, this response seems complete and correct correct.

In the next step I send this URL to ConnectIQ like so to retrieve my devices:

let devices = ConnectIQ.sharedInstance().parseDeviceSelectionResponse(from: url)

This returns back an array of IQDevice objects, as expected, which for me is one device: an Edge 520. However, the device has a UUID that has a value of 00000000-0000-0000-0000-000000000000.

[IQDevice: 0x7003e220, uuid = 00000000-0000-0000-0000-000000000000, modelName = "Edge 520", friendlyName = "Edge 520"]

Is this a known issue or user error? All subsequent calls with this device (such as ConnectIQ.sharedInstance().getDeviceStatus(device)) return predictably unhelpful results.

Former Member over 8 years ago

Hi there-
I see that the Edge software was rev'd to v9.1 in early Nov.

Did this update fix this underlying bug?

-DW

Former Member over 8 years ago

I missed your post on messaging until now. Pardon the delay.

The iOS SDK does not work for anyone attempting to developing an iOS app with and Edge device (maybe more?). It's irresponsible to limit this knowledge to -- as best I can tell -- this thread. It's very clear that you and team are attempting to create a world-class developer platform -- and you are doing quite well. Communicating successes and issues, is part of that.

A good place to put a notice about the iOS SDK's SEV-0 would be above the download link for the SDK itself, or in the iOS SDK programmers guide. These are logical, well-scoped places to ensure developers attempting to use the SDK understand the current limitations. Having managed developer ecosystems in the past, such prominent notices, while painful, serve as a good incentive to get it fixed asap and keep goodwill with the developers you are hoping to court.

Coleman.Apps over 8 years ago

Hello,

And sorry for the delayed response. We have been out of office for the holiday since Wednesday of last week. We have decided that a link to the known issues thread will be included in the Readme that is downloaded with each SDK. We do our best to get the right information to our developers in the most appropriate ways. We always appreciate your feedback and suggestions about anything related to Connect IQ.

Thank you,

-Coleman

Former Member over 7 years ago

Hello,
it is almost one year, and it is still not working. Do you think, that it will sometimes in the future work? iOS 10, iPhone 5s, Edge 520 - still UUID = 0x0

Thank you very much :)
Matus

Former Member over 7 years ago

This is clearly not a priority. What's unclear is why they don't take the iOS SDK down from the docs since it does nothing it promises. I've abandoned my project and the platform as a result of months of stagnation. Here we are a year later and nothing has changed...

Solace knowing I wasn't the only one trying to use it. Here's to hoping it pops to the top of their queue eventually!