Auth0Provider user is not used when a custom profile route is set

[seanparmelee]

Checklist

• The issue can be reproduced in the nextjs-auth0 sample app (or N/A).
• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

The Auth0Provider allows for an initial user to be passed, which is used as the fallback value for the /auth/profile route:

nextjs-auth0/src/client/providers/auth0-provider.tsx

Line 19 in 611c691

"/auth/profile": user

The issue is that if a custom profile route is set to something other than /auth/profile, then the initial user will not be used.

Reproduction

1. Configure a custom profile route via the NEXT_PUBLIC_PROFILE_ROUTE environment variable. (ex: NEXT_PUBLIC_PROFILE_ROUTE=/api/me.
2. In a server component, fetch a user and pass it to the Auth0Provider:

const session = await auth0.getSession();

...

return (
  <Auth0Provider user={session?.user}>
    {children}
  </Auth0Provider>
);

3. In a child client component, use the useUser() hook to retrieve the user and render a field, such as the sub:

const user = userUser()

...

return (
  <div>User: {user?.sub || 'undefined'}</div>
);

4. Log into your application and navigate to a page that uses the component from the previous step.
5. Since the user was already fetched in a server component, the user's sub should immediately be rendered on the page, but notice that it briefly renders "undefined" first.

Additional context

No response

nextjs-auth0 version

4.0.3

Next.js version

14.2.24

Node.js version

22.14.0