After successful Google auth login screen is briefly visible

[timukasr]

After authenticating via Google, when user is redirected back to site, <Unauthenticated> section is shown briefly, before state is updated and logged in (<Authenticated>) state is shown.

It seems that isAuthenticated is false for about one second. Then it is updated to show correct value:

{date: '2025-11-15T20:42:10.392Z', isLoading: true, isAuthenticated: false}
{date: '2025-11-15T20:42:10.655Z', isLoading: false, isAuthenticated: false}
{date: '2025-11-15T20:42:11.107Z', isLoading: false, isAuthenticated: false}
{date: '2025-11-15T20:42:11.154Z', isLoading: false, isAuthenticated: false}
{date: '2025-11-15T20:42:11.349Z', isLoading: false, isAuthenticated: true}

Issue occurs only with "@convex-dev/auth": "^0.0.90"
With 0.0.89 it is working as expected -isLoading is true until isAuthenticated becomes true.

{date: '2025-11-15T20:44:01.171Z', isLoading: true, isAuthenticated: false}
{date: '2025-11-15T20:44:01.549Z', isLoading: true, isAuthenticated: false}
{date: '2025-11-15T20:44:02.010Z', isLoading: true, isAuthenticated: false}
{date: '2025-11-15T20:44:02.059Z', isLoading: true, isAuthenticated: false}
{date: '2025-11-15T20:44:02.200Z', isLoading: false, isAuthenticated: true}

Can be reproduced with https://github.com/get-convex/convex-auth-example after updating dependencies.

[Fanzzzd]

Same problem here
You can add a custom isLoading state to avoid this.

const user = useQuery(api.users.getCurrentUser);
const state = useConvexAuth();
const isLoading = user === undefined || state.isLoading;

I’ve found that the client-side isLoading from useConvexAuth flips a few milliseconds before we can actually get the userId and related auth information from the backend. I’m not sure if this is an intentional design or an unintended behavior.

Personally, I’d expect that once useConvexAuth’s isLoading is false, we’d immediately be able to fetch auth information from the backend — that model fits my brain better.

[timukasr]

I'm observing something different what @Fanzzzd described.

This the query function to get user:

export const viewer = query({
  args: {},
  handler: async (ctx) => {
    const userId = await getAuthUserId(ctx);
    return userId !== null ? ctx.db.get(userId) : null;
  },
});

On the client, doing this:

  const { isLoading, isAuthenticated } = useConvexAuth();
  const user = useQuery(api.users.viewer);
  console.log({ date: new Date().toISOString(), isLoading, isAuthenticated, user });

With convex-auth 0.0.89, this is the output:

{date: '2025-11-16T08:49:26.331Z', isLoading: true, isAuthenticated: false, user: undefined}
{date: '2025-11-16T08:49:26.694Z', isLoading: true, isAuthenticated: false, user: undefined}
{date: '2025-11-16T08:49:27.199Z', isLoading: true, isAuthenticated: false, user: null}
{date: '2025-11-16T08:49:27.255Z', isLoading: true, isAuthenticated: false, user: null}
{date: '2025-11-16T08:49:27.408Z', isLoading: false, isAuthenticated: true, user: {…}}

Notice that user value changes from undefined -> null -> value. But auth.isLoading === true the entire time so we can ignore user during loading. Also, I don't observe the "few ms delay" @Fanzzzd mentioned - user becomes non-null, auth.isLoading becomes false in the same moment.

With convex-auth 0.0.90, user behavior is the same (undefined -> null -> value), but auth.isLoading becomes false earlier so no way to know that user === null is "wrong" info:

{date: '2025-11-16T08:50:44.691Z', isLoading: true, isAuthenticated: false, user: undefined}
{date: '2025-11-16T08:50:45.126Z', isLoading: false, isAuthenticated: false, user: undefined}
{date: '2025-11-16T08:50:45.729Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.780Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.931Z', isLoading: false, isAuthenticated: true, user: {…}}

[Fanzzzd]

This shows in my console:

{date: '2025-11-17T14:07:10.434Z', isLoading: true, isAuthenticated: false, user: undefined}
{date: '2025-11-17T14:07:10.450Z', isLoading: false, isAuthenticated: true, user: undefined}
{date: '2025-11-17T14:07:10.452Z', isLoading: false, isAuthenticated: true, user: {…}}

So there is no logs like

{date: '2025-11-16T08:50:45.729Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.780Z', isLoading: false, isAuthenticated: false, user: null}

Im using the same code you provided with "@convex-dev/auth": "^0.0.90" and using google as provider.

Maybe you can provide more information about this issue.

BTW I think my observation:

"I’ve found that the client-side isLoading from useConvexAuth flips a few milliseconds before we can actually get the userId and related auth information from the backend. I’m not sure if this is an intentional design or an unintended behavior."

also shows in your 0.0.90 log:

{date: '2025-11-16T08:50:44.691Z', isLoading: true, isAuthenticated: false, user: undefined}


{date: '2025-11-16T08:50:45.126Z', isLoading: false, isAuthenticated: false, user: undefined}  
^^ at this moment isloading become false and user is still undefined

{date: '2025-11-16T08:50:45.729Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.780Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.931Z', isLoading: false, isAuthenticated: true, user: {…}}

[Fanzzzd]

After several attempts, I successfully recorded logs similar to the following when returning from Google login

{date: '2025-11-16T08:50:45.729Z', isLoading: false, isAuthenticated: false, user: null}
{date: '2025-11-16T08:50:45.780Z', isLoading: false, isAuthenticated: false, user: null}

I haven't thought of an easy way to solve this problem yet. Perhaps we can downgrade and wait for this issue to be fixed/