Complete

disallowed_useragent on oauth flow for google services

Hello, I want to report a problem with google oauth services which is a real stopper for creating good experiences on devices.

This is not a new bug neither a new change on google policies, this was already reported on another post like 3 years ago, so I expected this to be fixed, but it is not.

Google does not allow an oauth authentication flow on embebed web-views, or at least on web-views with an unknown user agent. They report disallowed_useragent error when the garmin connectiq app opens the oauth flow.

Please, use the default browser or at least provide an appropriate user-agent for the web-view.

I have a watch face that shows next calendar events ready but I can not publish or even use it due to this problem.

Former Member
Former Member
  • Former Member
    Former Member in reply to Former Member

    Hello what are the technical limitations that are not allowing you to do so? There are hundreds of apps using google oauth without a problem.

    I know it is unfair that they impose such restrictions, but they are the big ones here and I think this leaves connect-iq and it's developers in a bad position in comparison to other actors.

  • Former Member
    Former Member

    You are correct that this has already been reported. In order to use google's oauth flow you would need to implement this in a partner app. We don't have a way to do this on device.