Watch face and OauthFlows

Former Member over 5 years ago

Hello,

I want to create a watchface that shows your next calendar events.

I don't want to build a companion app, so I just created an Oauth flow that asks for google calendar read-only events permissions. The have created also a small endpoint that reduces the amount of data send by the google API.

Now I'm looking for proper examples of implementing the Oauth flow for my watch face and I can't find any proper reference on the developers guide. Where is the complete flow example? The only example I found is the strava api, and for my understanding, it makes some unnecessary extra steps like creating a behavior delegate that does nothing (why do they do that) and show a login screen. I don't want to sow a login screen, If the user is not logged, then I will show nothing and that's enough for my project.

Can I just register directly for oauth on app initialization? Should I provide a delegate ven if I don't need it?

Thanks for your help

Top Replies

jim_m_58 over 5 years ago in reply to jim_m_58 +1

In the thread I linked to, there was a really simple example of a WF with a background process, with a bunch of println calls, but it may have gotten lost when the forums changed in April. Here's the same…

All Replies

Former Member over 5 years ago

What the hell?

Details: Module 'Toybox.Communications' not available to 'Watch Face'

Why, why in the world I can't decide which permissions I grant to a watch-face? Why can it not do any kind requests? I don't understand it!!

On the documentation it says that watchface just requires permissions, not that is completely impossible. This made me loose lot of time. Don't even get it.

What are the alternatives? Can I fetch this information from a companion widget?

HermoT over 5 years ago in reply to Former Member

You can only do web requests in a watch face using background process. So you need the background permission for the watch face as well.

Have a look at temporal event.

Former Member over 5 years ago

Well, just for not completely wasting my oauth flow I'm creating a widget that uses it (while I clarify if it is possible to communicate a widget with a watchface).

Something I noticed is that there is only one option about response type to provide to the makeOauthRequest. My latest endpoint returns a JSON and I want to extract the values from it. I tried providing HTTP_RESPONSE_CONTENT_TYPE_JSON as response type but that does not makes it take anything out of the response bode. Seems that they only option is to read request params. If that is true it is very limiting. I can make a last redirect to a superfluous page and put the token there as a workaround, but I still think it feels limiting.

Former Member over 5 years ago in reply to HermoT

Ok, I'm open to request background permissions (in fact I think I did already, but whatever).
Can I initialise an oauth flow from there ? Can at least open a web-page on the device from there? I need to authenticate the user in some way

HermoT over 5 years ago in reply to Former Member

Widget and watchfaces, or any other app cannot communicate with each other.

HermoT over 5 years ago in reply to Former Member

Have you checked if there are any examples in the sdk samples folder? Or in the sticky here

forums.garmin.com/.../overview-of-connect-iq-apps-accompanied-with-source-code

Former Member over 5 years ago in reply to HermoT

Yep, I took a look at the sdk samples folder and I can only see the strava example. I'll take a look at that sticky, its a great source.

Former Member over 5 years ago in reply to HermoT

That's sad, Will open an entire world of companion widgets . I tought I read it somewhere... maybe just in a dream.

Former Member over 5 years ago in reply to HermoT

Just remembered that the crystal (open source) watchface has a background method for fetching the whether. I'll see if I can use there the oauth flow. Thanks!!

jim_m_58 over 5 years ago in reply to Former Member

Here's a whole thread about backgrounding in general:

https://forums.garmin.com/developer/connect-iq/f/discussion/5287/very-simple-sample-of-a-watch-face-with-a-background-process/42557#42557