[SOLVED] getLoggedInUser of Google OAuth SSR gives null once logged in success

I'm really sure there is bug. Step to reproduce:

1. download this project https://github.com/appwrite/demos-for-react/tree/master/nextjs/server-side-rendering
2. Change OAuth sign in, from Github with Google

"use server";

import { createAdminClient } from "./appwrite";
import { headers } from "next/headers";
import { redirect } from "next/navigation";
import { OAuthProvider } from "node-appwrite";

export async function signInWithGoogle() {
  const { account } = await createAdminClient();

  const origin = headers().get("origin");
  const successUrl = `${origin}/oauth`;
  const failureUrl = `${origin}/signin`;

  const redirectUrl = await account.createOAuth2Token(
    OAuthProvider.Google,
    successUrl,
    failureUrl
  );

  redirect(redirectUrl);
}

3. npm run dev
4. Sign in with google
5. You will redirect to sign in page because of below lines. Means, getLoggedInUser is null.

// app/account/page.tsx
const user = await getLoggedInUser();
if (!user) redirect("/signin");

6. Refresh the page, then you will be redirected to /account page.

Maybe there is some delay, with the session, i'm not sure, but I have checked my local browser, and session in Appwrite console exist.

I think I ran into a similar problem the other day. It's how Next handles redirects from what I can tell. The way I fixed it was by adding the cookie to the NextResponse as well at the end before returning it in /app/oauth/route.ts

const response = NextResponse.redirect(`${request.nextUrl.origin}/account`);
response.cookies.set(SESSION_COOKIE, session.secret);
return response;

Wahh, thank you for your help. It works like you said. need to add the cookie. Thanks a lot @Ryan

[SOLVED] getLoggedInUser of Google OAuth SSR gives null once logged in success

No worries, I'll see if I can put in a PR/issue to update the repo