From 0b2b61ee2d34f2789341d281e966fa117933decc Mon Sep 17 00:00:00 2001
From: Vadym Samoilenko <vadymsamoilenko@oliver.agency>
Date: Mon, 23 Mar 2026 14:46:43 +0000
Subject: [PATCH] fix: call fetchMe after token acquire regardless of loading
 state
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

loading starts as true in the store, so the previous condition
`!user && !loading` prevented fetchMe from ever being called after
the Azure AD redirect — causing a permanent Loading spinner.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 frontend/src/App.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frontend/src/App.tsx b/frontend/src/App.tsx
index d07cdc5..6d5d865 100644
--- a/frontend/src/App.tsx
+++ b/frontend/src/App.tsx
@@ -38,7 +38,7 @@ function AuthGate({ children }: { children: React.ReactNode }) {
           scopes: ['openid', 'profile', 'email'],
         })
         setToken(result.idToken)
-        if (!user && !loading) fetchMe()
+        if (!user) fetchMe()
       } catch {
         instance.loginRedirect({ scopes: ['openid', 'profile', 'email'] })
       }