> 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/open-auth-in-real-browser-not-webview.md).

# Why does provider OAuth fail in my app's web view?

Provider OAuth pages restrict iframes, sandboxed windows and embedded WebViews (which hide the URL bar), so identity providers like Google block them and the consent buttons become unresponsive.

**Open the auth URL in a real browser:**

* **Mobile:** use an in-app browser component such as `react-native-inappbrowser-reborn`, never a raw WebView.
* **Web:** open a normal new tab or window with a visible, editable URL bar.

The [authentication flow](https://docs.tryterra.co/health-and-fitness-api/user-authentication/authentication-flow) then completes just as it does from the dashboard.

For web-API providers like Strava, also:

{% stepper %}
{% step %}
Create your API credentials.
{% endstep %}

{% step %}
Set the authorization callback domain to `api.tryterra.co`.
{% endstep %}

{% step %}
Add the credentials under [Connections settings](https://github.com/tryterra/api-faqs/blob/main/dashboard/connections/README.md) in the Terra dashboard.
{% endstep %}
{% endstepper %}


---

# 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/open-auth-in-real-browser-not-webview.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.