Dice Lock's Google sign-in on Android works againSigning into Dice Lock with a Google account on Android works again

October 21, 2026 · Google sign-in on Android was quietly refusing every real player; Dice Lock's own server now checks the token itself, and the invite links finally explain how to get into testing.Signing into Dice Lock with Google on Android was quietly failing; the game's own server now checks sign-ins itself, and the invite links finally explain how to get in.
last updated

Google sign-in on Android works again

The owner reported it from their own phone: signing into Dice Lock on Android with a Google account answered "the sign-in service refused that credential. You are not authorized to perform this request." Production logs showed Clerk turning down the real Credential Manager token with 403 authorization_invalid, while a deliberately junk token got a different error, 400 google_one_tap_token_invalid, which ruled out the first guess, a wrong audience value. The genuine token was reaching Clerk's check and failing inside it. The field actually being refused was azp, which names the OAuth client that asked Google for the token; Credential Manager fills that in with Android's own client id, and nothing in the request can change it. Clerk's Google One Tap strategy has no setting for it, and another Android app had reported the identical sentence earlier that same month, so this wasn't a one-off misconfiguration on Dice Lock's side.

The fix stopped asking Clerk to make that check at all. Dice Lock's own server now verifies the Google token itself, directly against Google's public signing keys, confirms it was issued for the right client, looks up or creates the Clerk user who holds that verified email address, and mints a sixty-second sign-in ticket that gets redeemed the same way an Apple sign-in already does. No update to the Android app was needed, since the phone was already sending the right token; only the server had to change. Getting that change live took longer than writing it did: Railway, which hosts the game's server, declared a platform-wide build outage that afternoon, and the fix sat finished and undeployed for hours alongside two unrelated pushes, until a deploy script retrying every few minutes finally got one through.

The invite doors finally say how to get in

The three invite links on the Dice Lock homepage, one each for iPhone, Android and browser, all used to read "Join the test." That worked for iPhone, where the TestFlight link opens to anyone who clicks it, but it was wrong for Android: Google's beta only opens to an email address already on the tester list, so a visitor who clicked through was landing on a page that quietly turned them away with no explanation. At the owner's instruction, the iPhone door now reads "Join via TestFlight", the one deliberate exception carved into a standing rule that nothing on the landing page names the programme by name, and the Android door now reads "Share your email with the admin first."

That's a small fix sitting on top of a much bigger backdrop. A good share of the day's dice-lock commits, more than sixty of them, went toward getting the Android store listing itself submission-ready: a file of the exact boxes Google's console asks for, sized differently from Apple's because Google's actual screenshot ceiling turned out to be a 2.3 aspect ratio rather than the shape the ticket had assumed, found by uploading five shapes to a throwaway listing and reading back the rejection; and a script that reads the live listing back from Google's own API and reports each field as MATCH, DIFFERS or EMPTY. A separate fix that day caught a genuine undercount: the internal stats page's tile for linked accounts read 4 while ten accounts had actually linked, because the analytics queue waited for a browser tab to go hidden before flushing, and iOS suspends that kind of request mid-flight before it lands. A sign-in now flushes the queue immediately instead of waiting for the tab to hide. None of these pieces is dramatic alone, but together they're the difference between a store listing that's theoretically ready and one that's actually ready to submit.

Signing in with Google on Android works again

The owner reported this one from their own phone: trying to sign into Dice Lock on an Android phone with a Google account came back with a vague error saying the sign-in was refused and not authorized. Looking at the game's server logs showed that Clerk, the outside service Dice Lock uses to handle sign-ins, was rejecting the real sign-in attempt with one error, while a fake, made-up one got a different error. That ruled out the first guess, that the wrong app identifier was being sent, and showed the real sign-in was reaching Clerk's check and failing there specifically. The actual problem was a mismatch in which app Clerk expected the request to have come from: the way Android hands over a Google sign-in fills in a detail naming the Android app itself, and Clerk's particular method of checking a Google sign-in has no setting that can account for that. Another, unrelated Android app had hit the exact same wall earlier that month, so this wasn't something Dice Lock had set up wrong on its own.

Rather than wait for that check inside Clerk to be fixed, the game stopped relying on it. Dice Lock's own server now checks the Google sign-in itself, confirms it was meant for this app, finds or creates the matching account, and hands Clerk a short-lived pass that lets the person in, the same trick already used for signing in with Apple. No update to the Android app itself was needed, since the phone was already sending the right information; only the server behind it had to change. Getting that change live took longer than writing it, though: the company that hosts the game's server had a company-wide outage that afternoon and stopped accepting new deployments for everyone, not just this game. The fix sat finished but unable to reach players for hours, alongside two unrelated updates, until a script that kept retrying every few minutes finally got one through.

The Dice Lock website has three buttons inviting people to try the game early, one each for iPhone, Android and playing in a browser, and all three used to say "Join the test." That wording worked for iPhone, where the testing link works for anyone who clicks it. It was wrong for Android, where Google only lets in people whose email address has already been added to an approved list by hand, so someone clicking the Android button was landing on a page that quietly turned them away without saying why. The owner asked for this to be fixed directly: the iPhone button now says "Join via TestFlight" (TestFlight being Apple's name for its testing program, named here as a one-time exception to a rule that the site otherwise never names it), and the Android button now says "Share your email with the admin first."

That's a small fix next to a much bigger effort behind it. Most of the day's work on Dice Lock, more than sixty separate changes, went toward getting the Android app's store listing ready to submit: a document laying out what goes in each box of Google's submission form, sized differently from Apple's because Google's screenshots turned out to need a narrower shape than the ticket had assumed, discovered by uploading five test shapes and reading back which ones Google's system rejected; and a checking script that reads the real listing back from Google and reports, box by box, whether it matches, differs, or is still empty. A separate fix that day caught a genuine counting mistake: an internal page meant to count how many players had linked an account was showing 4 when ten accounts had actually been linked, because the tracking system was waiting for the app to go into the background before sending that information, and iPhones often cut that kind of request off before it finishes. Signing in now sends that information right away instead of waiting. None of these pieces looks dramatic on its own, but together they're the difference between a store listing that looks ready and one that's actually ready to submit.