Signing into Dice Lock now posts every score on your device at onceSigning into Dice Lock now posts every score on your device at once

September 30, 2026 · Dice Lock guests can now sign in from any finish and get every score on their device onto every leaderboard at once, plus a docs-render bug fix.Dice Lock guests can now sign in from any finish screen and see every score on their device post to every leaderboard at once, and a docs bug got fixed.
last updated

Every score on your device, posted at once

A Dice Lock player with no Apple ID and no Google account, or one who had signed up on the website instead, could not get into the iPhone app at all before Tuesday morning. Both of its doors ran through someone else's company. JIO-1564 built a third one, with email and password fields under the two provider buttons, but testing it against production turned up two things the original ticket had gotten wrong. Clerk flags this instance's sign-ins needs_client_trust, not the needs_second_factor a server checking the standard two-factor path would look for, so a server written straight from the docs would have refused every sign-in it received. And Clerk asks for the six-digit code on every single attempt, not only from a new device, because trust lives on the Clerk client object and this server starts a fresh one each time. The form now says a code is on its way rather than treating that as something gone wrong.

That shipped at 2:22pm, and it turned out to be the first step of a longer day. Next came a sign-in door at the bottom of every finish screen (Endless, Versus, Tower, Puzzles, the Daily), telling a guest exactly where that run would land on the mode's board, before they had signed into anything. Behind that door sat a sharper question: once someone does sign in, what actually gets posted? Until the evening, the answer was whatever they had just played. A guest who had set personal bests across five different modes over the course of a day, then pressed SIGN IN from one finish screen, got exactly one of those onto the boards. Just the mode on screen at the time. Everything else stayed invisible until replayed. A fix shipped at 6:55pm: a sign-in or a claimed username now posts every best the device is holding, across every mode, in one pass.

The last piece landed at 9:34 that night. Apple and Google sign-in on the web can answer through a full page redirect (the browser leaves for the provider's own page and comes back as a fresh load), which describes most sign-ins made from an iPhone's browser rather than the app itself. The screen meant to confirm the backfill does not survive that round trip, so the most common path showed no sign that anything had happened. The pending sign-in marker now remembers where the original press was made, and the Account screen gained a new section, "on the boards," listing a standing per leaderboard, so a sign-in that bounces through a redirect still lands somewhere that shows it worked.

A finished diagram that logged itself as a failure

A documentation run early that same morning was recorded as failed at 6:14am, even though a complete, correct architecture diagram was sitting right there in its own error output. Headless Chrome had printed the whole page, then hung while shutting itself down, and its own ten-second watchdog killed the process before it could exit cleanly. The code that runs Chrome throws on any non-zero exit, so the crash reached the pipeline before anything looked at what Chrome had actually drawn.

The fix checks the output instead of the exit code. If the dump ends in a closing </html> tag, Chrome reached its own last byte, so the render counts as a success, with the exit code logged rather than hidden. Anything short of that closing tag is still a real failure. The same bug was sitting in the screenshot code, fixed the same way by checking for a complete PNG instead of trusting Chrome's exit status. Chasing it down also turned up a test that no longer matched reality: it assumed that pointing Chrome at a dead port still produces a screenshot of a generic error page, which stopped being true on the Chrome version now running. A dead port now writes no file at all, while a live server's 404 page still gets photographed as if it were ordinary content. The test now checks the case that actually matters.

Every score on your device, posted at once

Before Tuesday morning, if you played Dice Lock on an iPhone with no Apple account and no Google account (or you'd made your account on the game's website instead), there was no way into the app at all. Both of its sign-in buttons led through one of those two companies. A new one was added: an email address and a password, right on the app's own screen. Testing it against the real live game turned up two surprises. The login service the game uses, a company called Clerk, reports this kind of sign-in with a label meaning "we don't trust this device yet," not the label a server would normally check for when asking for a verification code. And Clerk asks for that six-digit code by email on every single attempt, not just the first time on a new phone, because of how it decides which devices it trusts. So the app now tells the player a code is coming, instead of treating that as something wrong.

That went out at 2:22 in the afternoon, and it turned out to be the first step of a longer day. Next came a sign-in button at the bottom of every finish screen (after an Endless run, a match, a Tower climb, a puzzle, the daily challenge), telling a guest exactly where that result would land on the leaderboard, before they'd signed into anything. That raised a sharper question: once someone does sign in, what gets posted? Until that evening, the answer was whatever they'd played most recently. A guest with good scores in five different parts of the game, who signed in after finishing just one of them, got only that one onto the leaderboards. Everything else stayed invisible until replayed. A fix went out at 6:55 that evening: signing in, or picking a username, now posts every saved score at once.

The last piece landed at 9:34 that night. Signing in with Apple or Google on the web can work by sending the browser to that company's page and back as a new page load, which is how most sign-ins happen in Safari on an iPhone rather than the app. The screen meant to show "all your scores just got posted" doesn't survive that trip, so the most common way of signing in showed no sign anything had happened. The game now remembers where the button was pressed, and the Account screen gained a section listing the player's standing on each leaderboard, so a sign-in taking that detour still proves it worked.

A finished picture that reported itself as broken

A documentation job that runs automatically every morning was marked as failed at 6:14am, even though a complete, correct picture of the system's architecture was sitting right there in its own error output. The job draws that picture using a web browser with no visible window, called headless Chrome. Chrome finished drawing the whole page, then got stuck shutting itself down, and its own ten-second safety timer killed the process first. The code running Chrome treats any abnormal shutdown as a failure, so the crash got reported before anything checked whether the picture was actually right.

The fix checks the actual output instead of how Chrome shut down. If the saved page ends with the closing tag marking a complete web page, Chrome finished drawing before it got stuck, so the job now counts as successful, with the odd shutdown logged as a note rather than hidden. Anything cut off before that tag is still a real failure. The same mistake was sitting in the screenshot code, fixed the same way by checking for a complete image file instead of trusting how Chrome exited. Tracking this down also turned up a stale test: it assumed pointing the browser at an address that doesn't exist would still produce a screenshot of a generic error page, which stopped being true on the Chrome version now running. A truly dead address now produces no file at all, while a live server saying "page not found" still gets photographed as if it were normal. The test now checks the situation that actually comes up.