On 3 November I looked at 14 days of visitor data for one form on my site.

Five people had started filling it in and never finished. Four of them had pressed Continue with Google. Then nothing. They never came back.

The button itself wasn't broken. So where did they go?

Where they came from

My site is TrustCheck, and a lot of our visitors arrive from links shared on X, Instagram and Facebook.

When you tap a link inside those apps, it doesn't open Chrome or Safari. It opens the app's own built-in browser. And Google refuses to sign people in inside those built-in browsers. The person taps the button, gets an error page from Google, and closes the tab.

From my side, nothing failed. No error. No log line. Just a person who left.

The errors I was ignoring

What made it worse: I had been looking at errors from those same browsers for days, and filing them as junk.

My visitor insights kept recording "page errors" like:

Can't find variable: CONFIG currentInset webkit.messageHandlers 

None of that is my code. The X, Facebook, Instagram and TikTok in-app browsers inject their own scripts into every page, and those scripts throw errors. On 1 November I filtered them out so they'd stop polluting my error counts:

public static function isNoise(?string $label): bool { return (bool) preg_match( '/CONFIG|currentInset|webkit\.messageHandlers|__gCrWeb|instantSearchSDKJSBridge|WeixinJSBridge/', (string) $label ); } 

Two days later I found out the same browsers were also quietly breaking my sign-in. The noise was a clue, and I had filtered it away.

The fix: a code by email

I didn't want to fight Google's rules. So I added a second way in that never leaves the site: type your email, get a 6-digit code, type it back.

Email code is now the first option on that form. Google is second.

The parts I cared about:

  • The code lives for 10 minutes, stored hashed, never in plain text.
  • 5 wrong tries and the code is dead.
  • At most 3 codes per email address in 10 minutes, so nobody can use the form to flood someone's inbox.
$code = (string) random_int(100000, 999999); Cache::put(self::key($email), [ 'hash' => password_hash($code, PASSWORD_DEFAULT), 'tries' => 0, 'sent' => $recent, ], 600); 

Checking it uses password_verify() and deletes the code on success, so it can't be used twice.

On my laptop the code is written to the log instead of being emailed. I never want a test run to email a real person.

What I'd check on your site

If any of your traffic comes from social media, open your own site from inside the X or Instagram app and try to sign in. It takes two minutes.

I only saw this because I was counting where people stopped, not just what errored.

Have you found a bug that only happens inside in-app browsers? What was it?