Describe the bug
If I return to a logged in state page after some time, the AuthUser from context doest not contain any email data in it.
While the client side shows the logged in state correctly.
Once I log out and log back in, everything starts working.
We decide on making certain api calls only if the user is logged in on server side, but in this case it breaks, as client seems to say user is logged but thats not the case on server ?
Describe the bug If I return to a logged in state page after some time, the AuthUser from context doest not contain any email data in it. While the client side shows the logged in state correctly. Once I log out and log back in, everything starts working. We decide on making certain api calls only if the user is logged in on server side, but in this case it breaks, as client seems to say user is logged but thats not the case on server ?
Trying to understand what can cause such a scenario. I have verified all the cookies are set correctly in
next-firebase-auth
config.