[IkeyBenz]

What PR #75 was trying to fix

PR #75 (e3a06b2) fixed a blank green screen that appeared when opening a game link directly (e.g. /games/1234). The root cause was that the splash screen hid before auth completed.

Why PR #75's approach introduced new race conditions

PR #75 changed AuthProvider to use onAuthStateChanged and set isLoading=false immediately when the user was detected, refreshing the token in the background (fire-and-forget). This meant:

• userId was set and isLoading was false BEFORE the token refresh completed
• Downstream code like useCreateGame checks isLoading and userId before calling getIdToken()
• Since both were ready before the token was actually refreshed, API calls could use stale/invalid tokens

What this fix does differently

This fix keeps onAuthStateChanged (which is faster than signInAnonymously for returning users since Firebase caches auth state) but awaits the token refresh before setting isLoading=false:

auth.onAuthStateChanged(async (user) => {
  if (user) {
    setUserId(user.uid);
    await user.getIdToken(true); // Wait for token refresh
    setIsLoading(false);         // NOW auth is truly ready
  }
});

This ensures:

• ✅ Splash screen stays visible until auth + token are BOTH ready
• ✅ No green screen on direct game links
• ✅ No token race conditions (getIdToken always returns valid token)
• ✅ Fast auth for returning users via cached onAuthStateChanged

How it was tested

1. Game creation: Created a game with username, navigated to lobby — no token errors
2. Direct link: Navigated directly to /games/{PIN} — game loaded correctly, no green screen
3. Verified splash screen stays visible during auth loading

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
modi-app	Ready	Preview, Comment	Feb 8, 2026 6:31pm