Social Login (Facebook/Google) Issues in Bubble Native Mobile – Deep Link, redirect_uri, and Session Sync

Mobile Beta
1

Hi everyone,

I’m running into multiple issues implementing social login (Facebook and Google) in a Bubble Native Mobile app and would appreciate insights from anyone who has successfully solved this.

Context

  • App built with Bubble Native Mobile

  • Testing via BubbleGo and TestFlight

  • Using Facebook Login and Google Login

  • Also tested web-based OAuth flow

Issues encountered

  1. “Login with a web browser” (mobile action)

  • Triggers OAuth, but forces a redirect_uri like:

    app-xxxxx://auth

  • This is a deep link (non-https), which:

    • Cannot be properly registered in Facebook/Google consoles

    • Causes invalid redirect_uri errors

  1. External web login workaround

  • Open external page (/login_fb, /login_google)

  • Run OAuth via Bubble web plugins

  • After login → trigger deep link back to app (mydomain://)

Problems:

  • Deep link sometimes not detected (especially TestFlight)

  • Requires user interaction (“Open app?” prompt)

  • Session is created in browser, not recognized in app

  1. Session sync issue

  • User logs in successfully via web

  • Returns to app via deep link

  • Current User in app is still logged out

  1. Auto-trigger limitations

  • Cannot reliably trigger OAuth on page load (browser blocks)

  • Requires button click (user gesture)

  1. TestFlight vs Production

  • OTA changes don’t apply to TestFlight

  • Deep link behavior inconsistent vs BubbleGo

Summary of blockers

  • redirect_uri mismatch (http vs custom scheme)

  • Deep link not reliably supported in OAuth providers

  • No shared session between web and native app

  • Bubble Native lacks clear mechanism for passing auth state back

Main question

:backhand_index_pointing_right: What is the definitive, production-ready approach for implementing Facebook/Google login in a Bubble Native Mobile app?

Specifically:

  • How to handle redirect_uri properly?

  • How to ensure the user is authenticated inside the app (not just in web)?

  • Is there a reliable pattern that avoids deep link/session issues?

Any working architecture or real-world implementation would be extremely helpful.

Thanks!

2

Instead of taking the user to external page.

Use webview element inside native view.

This fetches the current session of user and is synced.