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

I just built the Obj-C sample app, and the UUID from the same Garmin device was also 000...000. Perhaps this is expected behavior but it strikes me as weird. Furthering my suspicion is the query of ConnectIQ.sharedInstance().getDeviceStatus(device) returns not found or not connected when the device is connected.

Can someone confirm that UUIDs should *not* be 00000000-0000-0000-0000-000000000000?

Coleman.Apps over 8 years ago

Hello,

Thank you for all the detail. I hadn't heard of this, but I'm not certain on the expected behavior here. I've created a ticket for us to review.

Thanks again,

-Coleman

Former Member over 8 years ago

Gracias minas

Thank ya. I'm stopped dead in my tracks and eager to keep going. Anything I can do to help, please ask.

Former Member over 8 years ago

I was able to get the UUID sniffing the bluetooth channel and have unblocked my development.

But -- I can't distribute my app with my UUID hardcoded. So near-term crisis averted, but I would still like to help fix this bug so I can eventually use the SDK as intended.

Coleman.Apps over 8 years ago

I was able to find out a little bit more on this one. I totally missed the device info you provided so I apologize. There is a device issue right now with our Edge units that is causing problems with the iOS SDK. This is causing your issue. That one is a little outside our hands at the moment, but it is being worked on. Once there is an update to fix it you should be able to use the SDK as normal instead of your workaround.

Thank you for your patience,
-Coleman

Former Member over 8 years ago

Ok, I really appreciate the update lest I fumble needlessly.

Any idea on timing? Days, weeks or months? Any clues would help my prioritization.

Also, what devices does this not effect? I may just go by a new one to keep going.

Former Member over 8 years ago

Guidence

Any guidance on when this will be fixed or what, if any, other devices this bug effects?

Also, are you planning to update the documentation to warn other developers that the iOS SDK is broken for a significant family of devices, lest they run into the same problems?

Coleman.Apps over 8 years ago

Any guidance on when this will be fixed or what, if any, other devices this bug effects?

Also, are you planning to update the documentation to warn other developers that the iOS SDK is broken for a significant family of devices, lest they run into the same problems?

For a little further clarification. This issue is a result of the iOS SDK and non-wearable devices. The SDK is currently only supported over BLE protocol and not BT for these devices. The appropriate teams are aware of the issue, but we are unable to give any sort of ETA due to the nature of the issue itself. We appreciate your continued patience as we continue to do our best to support all of our developers in our growing developer community.

-The Connect IQ Team

Former Member over 8 years ago

I'm using BLE and BT interchangeably so thanks for the clarification I'll be more precise moving forward.

Thanks for the update on the defect. I can appreciate the lack of clarity given the various teams it must involve. I'll check back in a few months.

Are you going to update the Programmer's Guide with appropriate notice of this bug? It's good for others and selfishly it'd would help me spot when to jump back in :)

Coleman.Apps over 8 years ago

I'm using BLE and BT interchangeably so thanks for the clarification I'll be more precise moving forward.

Thanks for the update on the defect. I can appreciate the lack of clarity given the various teams it must involve. I'll check back in a few months.

Are you going to update the Programmer's Guide with appropriate notice of this bug? It's good for others and selfishly it'd would help me spot when to jump back in :)

We are working on some plans to better communicate any issues that are under investigation. The Programmers Guide will continue to be our "Perfect World" scenario where we explain how things should work. We are still discussing the best place to keep a list of issues. It will likely be a forum thread that is linked somewhere in the Programmers Guide, but we didn't feel it would be conducive to the flow of the Programmers Guide to intersperse known issues with the normal documentation. Hopefully this helps.

-Coleman