Session not reflected upon first login #171
Comments
|
@Rykuno Thank you for posting this issue. In development mode, the Next.js application (specifically NextAuth) was unable to connect to the Postgres database. I've pushed one commit which should fix that issue. Can you please pull the latest master branch and check if the issue still persists? |
|
Okay so I think I might have found a solution but not per say the issue. I do believe it is with the There's two issues.
I was able to solve both of these through configuring my _app.tsx as such but we lose auto static optimization from next due to the use of const MyApp = ({ Component, pageProps, router, session }: AppProps) => {
const apolloClient = useApollo(pageProps.initialApolloState, session?.token);
useEffect(() => {
if (router.asPath.endsWith("#")) router.push(router.pathname);
});
return (
<>
<Head>
<link rel="shortcut icon" href="/images/favicon.ico" />
</Head>
<NextAuthProvider session={session}>
<ApolloProvider client={apolloClient}>
<Layout>
<Component {...pageProps} />
</Layout>
</ApolloProvider>
</NextAuthProvider>
</>
);
};
MyApp.getInitialProps = async context => {
const appProps = await App.getInitialProps(context);
const session = await getSession(context);
return {
...appProps,
session
};
};
export default MyApp;Oh and on a side note volumes:
- ./migrations:/hasura-migrations
- ./metadata:/hasura-metadata |
|
@Rykuno Thank you for the detailed response. We'll most probably have to wait for both of these issues to be fixed in NextAuth rather than adding
Would you be interested in creating a PR for that? |
Created a PR for the volume issue. To reference the first issue I raised a question in the Next-Auth repo in which a response clarified the issue. I fixed this through moving the ApolloProvider initialization to a middleware layout of sorts to opt back into static optimization. There is probably a cleaner solution though. This issue occurs when you're redirected from signin directly to a page where data fetching utilizing apollo is required. The token would be undefined at this location in const createHttpLink = (token: string) => {
const httpLink = new HttpLink({
uri: process.env.NEXT_PUBLIC_API_URL || "http://localhost:8080/v1/graphql",
credentials: "include",
headers: token
? { Authorization: `Bearer ${token}` }
: { "X-Hasura-Role": `anonymous` },
fetch
});
return httpLink;
}; |
|
Hello! 👋 I believe I am running into a similar issue with this boilerplate, but I'm not entirely sure what the solution was. @Rykuno, would you mind elaborating further on what changes you made? Particularly the The issue I am seeing is that on first visit to the /feeds route after authentication, the token is undefined. If I refresh the page, the token is set and the route behaves as expected. I'm seeing this error in the console, too, which goes away after a refresh: |
Wish i could chime in here but I don't remember how I exactly solved the original issue. We migrated to firebase auth very soon after I fixed this. Their documentation was poor at communicating how it all worked. I created a ticket at the next-auth repoand got an explantation here |
|
No worries, thanks for the response! I think I have a workaround by wrapping each page with a If anyone can find a more elegant solution that preserves static generation, let me know :-) |
I noticed when initializing the app, the session within _app.js and subsequently apollo are not reflected with the users's creds.
It appears as the session goes through the callbacks of next-auth but is never reflected in the UI until a subsequent refresh.
I noticed by being unable to click the logout button within the nav right after signing in. I haven't dove into the issue as its late here but I'll see what I can find tomorrow and update with reproducible code need be.
The text was updated successfully, but these errors were encountered: