I use useSession({ required: true })
I sign out. I go to the page with the useSession. I am redirected to the signin page. I sign in and I go back to the protected page. I am again redirected to the signin page.
One more weird thing about this is, signIn works fine, and after this, when i went to another (client-side component put inside layout, session not required) page that simply displayed my session username, it showed my username without any issues
#session required error loop
flat owl
ebon cipherBOT
Hi @flat owl. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the information provided in the extracts, it seems like you're experiencing a loop issue with your authentication flow in Next.js. This could be due to a variety of reasons, such as incorrect routing, improper session handling, or issues with asynchronous operations.
One possible cause could be related to how you're handling authentication checks and redirects. As mentioned in the Next.js documentation (https://nextjs.org/docs/pages/building-your-application/routing/authenticating), you can use getServerSideProps to pre-render a page on each request using the data returned by getServerSideProps. If there's no session, you can return a redirect to the login page. This can prevent a flash of unauthenticated content before redirecting.
export const getServerSideProps = withSession(async function ({ req, res }) {
const { user } = req.session
if (!user) {
return {
redirect: {
destination: '/login',
permanent: false,
},
}
}
return {
props: { user },
}
})
Another possible issue could be related to how you're using router.push to navigate to different routes. As mentioned in one of the Github issues (https://github.com/vercel/next.js/issues/40554), invoking router.push more than once or trying to navigate to a page you're already on could cause issues.