Google OAuth: User Created But Session Not Recognized

SaimonOriginal post

Rank 1: Thread

Aug 5, 2026, 09:55

Problem Summary

When signing in with Google, the user is successfully created in the Appwrite console, but the session is not being recognized on the client side. The application keeps redirecting with "No active session found" error.

🔴 Issue Details

What's Happening

User clicks "Sign in with Google" button
OAuth flow completes
User appears in Appwrite console ✅
But client-side shows: No active session found
App continuously redirects (401 error)

Console Errors

react-dom_client.js?v=b7c8055c:14334 Download the React DevTools for a better development experience: https://react.dev/link/react-devtools

sgp.cloud.appwrite.io/v1/account:1  Failed to load resource: the server responded with a status of 401 ()

Profile.jsx:16 No active session found. Redirecting...

sgp.cloud.appwrite.io/v1/account:1  Failed to load resource: the server responded with a status of 401 ()

Profile.jsx:16 No active session found. Redirecting...

🔍 Current Code Flow

JavaScript

// Profile.jsx
const checkSession = async () => {
  try {
    const session = await client.account.get();
    // User data
  } catch (error) {
    console.log("No active session found. Redirecting...");
    // Redirect to login
  }
};

🙏 Request

Looking for guidance on:

Proper OAuth session handling in React
How to verify session after Google sign-in
Next steps to debug this issue

Summary

User is successfully created in Appwrite console, but the session is not recognized on the client side, causing continuous redirection with a "No active session found" error. The solution involves proper OAuth session handling in React, verifying the session after Google sign-in, and debugging to identify the issue causing the session recognition problem.