Questions

Has anyone successfully integrated Base44 authentication with a Median-wrapped iOS app while preserving existing Base44 accounts?

Our current login button uses Base44’s loginWithProvider('google'). After successful Google sign-in, the authenticated website appears to remain in a separate browser-style screen rather than returning to the main app WebView. Force-closing and reopening the app then shows a signed-out state.

Code inspection found no browser-to-app authentication handoff handler. We have not yet confirmed on-device whether the session exists only in the separate browser context.

We are considering Median’s Social Login plugin, but have not found a documented Base44 mechanism to exchange the returned Google ID token for a Base44 session. We also have not confirmed a supported secure browser-to-app callback flow.

Questions:

1. Is there a supported Base44 + Median integration for native Google sign-in?
2. Can the native Google ID token be exchanged for a Base44 session through an officially supported API or SDK method?
3. Alternatively, can Base44’s browser OAuth flow return to the main Median WebView and establish its session through a secure, single-use handoff?
4. How should that session persist across app restarts while preserving existing user IDs and account data?

We are looking for a supported authentication solution, not simply hiding browser controls, extending cookie expiry, or passing long-lived session tokens through deep-link URLs.

Official documentation, a working integration example, or guidance from Median/Base44 would be appreciated.