OAuth & Social Login

OAuth and social login flows (Google, Facebook, Apple, Microsoft, Auth0, etc.) are restricted inside standard mobile WebViews due to security policy blocks (throwing errors like 403 disallowed_useragent). To bypass these limitations securely, Nativine intercepts authorization request URLs, loads them inside a secure Chrome Custom Tab system browser context, and redirects the authentication parameters back to your WebView via deep link scheme redirection.

Integration Workflow

1. Interception: When the user initiates login and the WebView attempts to navigate to a common OAuth provider (e.g., Google, Facebook, Apple, Auth0, Okta, etc.), the app automatically opens the login flow in a secure Custom Tab.
2. Redirection: After completing the authentication on your site backend, redirect the Custom Tab back to your app using your deep link URL scheme:
   html

   myappscheme://oauth?token=JWT_TOKEN&refreshToken=OPTIONAL_REFRESH_TOKEN

3. Cookie Injection: When the app intercepts the deep link, it parses the query parameters, automatically writes them to your website domain's HTTP cookies, closes the Custom Tab, and refreshes the main app view to load the authenticated state.

Testing & Verification

To verify the setup, make sure your deep link scheme is configured in the builder settings and that your server-side callback redirects to [yourscheme]://oauth with the session credentials appended as query parameters.