> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/connecting/oauth-webview-and-sign-in-failures/oauth-webview-blocked-use-native-browser.md).

# Why does OAuth fail inside an in-app WebView?

Google blocks OAuth authentication inside **embedded WebViews** under its 'Use secure browsers' policy (the hidden URL bar prevents domain verification). This surfaces as 'Error 403: disallowed\_useragent' or a blocked screen, and also affects Fitbit's Google login.

**Replace the WebView with a native in-app browser** (Custom Tab or SFSafariViewController style) that shows the URL bar:

{% stepper %}
{% step %}
Open the Terra-generated auth URL in the native browser.
{% endstep %}

{% step %}
Handle the success and failure redirect URLs in your app.
{% endstep %}
{% endstepper %}

Your existing widget integration and redirect handling can stay the same. See [implementing the Terra widget](https://docs.tryterra.co/health-and-fitness-api/user-authentication/implementation-terra-widget) for the auth flow.

For Google Fit, the web API connection is recommended over the SDK path for reliability.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/connecting/oauth-webview-and-sign-in-failures/oauth-webview-blocked-use-native-browser.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.