Does Connect IQ mobile app's connectiq:// protocol handler support more than connectiq://oauth?

The ConnectIQ mobile app registers itself as a protocol handler for connectiq://. This allows oauth webpages to redirect to connectiq://oauth?<query params here> which is picked up by the mobile app and relayed to the device.

Does the connectiq:// protocol handler support any other features, perhaps even undocumented?

For example, it would be great if we could request connectiq://phoneappmessage?appid=xyz&field1=value1&field2=value2 which would relay to the device as a `Toybox.Communications.PhoneAppMessage`

0 Ultra over 2 years ago

I’m not even sure if it should be connectiq://<your IQ app name> rather than connectiq://oauth?

0 ksweber007 2 months ago in reply to Ultra

I've been using this mechanism for the past 18 months, and it suddenly stopped working.

It seems that the connectiq:// protocol handler in the Connect IQ app on iOS has changed — likely due to a recent update.

Previously, my auth token was successfully returned as a query parameter to the Garmin watch app, while at the same time the Connect IQ app confirmed that the login process had completed. Neither of these final steps happens anymore, and the watch app is now stuck waiting indefinitely for a response.

Can anyone confirm whether authentication via Connect IQ on iOS is still functioning properly for apps that require login?

I used the format connectiq://oauth?<query params here> as specified in the API @ developer.garmin.com/.../Authentication.html

0 ksweber007 2 months ago in reply to ksweber007

It’s working again now, after Garmin approved my recent watch app update - which took three days.

Interestingly, during the approval process, the Connect IQ protocol handler wasn’t passing the query parameters to the watch app, even after a successful OAuth flow.