From 15442150083988f342f38d9b5c881b7bf1857dd8 Mon Sep 17 00:00:00 2001 From: Talal Sharabi Date: Sun, 15 Mar 2026 15:57:12 +0400 Subject: [PATCH] Fix login response: return user directly instead of {user: ...} The SWR useUser hook expects the user object directly, but the login API was wrapping it in {user: ...}. This caused user.isVerified to be undefined after login, triggering the email verification gate. Made-with: Cursor --- src/pages/api/login.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/api/login.ts b/src/pages/api/login.ts index 6d259125..fb8a29fc 100644 --- a/src/pages/api/login.ts +++ b/src/pages/api/login.ts @@ -38,7 +38,7 @@ async function login(req: NextApiRequest, res: NextApiResponse) { req.session.token = data.token; await req.session.save(); - res.status(200).json({user}); + res.status(200).json(user); } catch (error) { console.error("Login error:", error); res.status(500).json({error: "Login failed"});