iOS: JS context appears to die/suspend ~4–5s into median.socialLogin.google.login() before callback, timeout, or any page-lifecycle event fires; no error, no Supabase Auth Log entry

On iOS only, tapping "Sign in with Google" (native social login, JavaScript Callbacks integration { callback } only, no redirectUri) opens the native Google auth surface, briefly starts loading accounts.google.com, then dismisses.

The user lands back on the app's splash/login screen with no error shown, and no failed or successful sign-in attempt appears in our downstream auth provider's logs (Supabase Auth). This does not reproduce on Android with the equivalent code path.

Current bridge version: median-js-bridge version: 2.18.1

We use the "JavaScript Callbacks" integration exclusively (per https://docs.median.co/docs/social-login-javascript-callbacks). We pass only callback, never redirectUri, specifically to avoid the "Server-side Redirects" mode navigating the webview away from our SPA.

Observed behavior on-device
All console output: including our heartbeat, which ticks every second, stops abruptly roughly 4–5 seconds after the native call is invoked. There is no "callback fired" log, no timeout-rejection log (well before our 30s timeout), and critically no pagehide/beforeunload/visibilitychange log either. Because the heartbeat itself stops rather than merely the callback going unanswered, this points to the entire JS context/page being suspended or destroyed; not a callback that's simply late or swallowed. Since nothing would remain running to log a heartbeat tick otherwise.

We think this could be a bug with the bridge specifically because we tried to point our Median app at the https://median.dev/social-login/callback-demo and it still failed the same exact way for Google sign-in on iOS specifically.