Replies: 1 comment
-
Hi Josh, it seems this message is just a little confusing but not an indicator of a problem. The cookies are unset successfully. See: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm relatively new to implementing next-firebase-auth, and I appear to have everything working properly from a core functionality perspective (the AuthUser object is correctly being populated with Firebase Auth user data; cookies are correctly being set and unset; redirects on authed/unauthed; protecting routes server-side; etc.).
However, when no Firebase user is currently logged into my app, I'm getting the following warnings in my Firefox browser console every time that I navigate to a page that's using withAuthUser() and useAuthUser():
The console warnings say that they are being generated from my ./pages/api/logout file (code below):
Example code below from one such page that is using withAuthUser() and useAuthUser() and generating the above console warnings when I navigate to it without a Firebase Auth user logged in:
When I've successfully logged in using one of the Firebase Auth methods, the above warnings go away in Firefox when I visit the same page.
I tried testing the same behavior in Chrome and the warnings do not appear there, so the issue appears to be Firefox-related. If it's relevant, the browser that I'm using is Firefox 90.0.2 on Mac OS 10.14.6.
I'd very much appreciate any advice that you can provide on how I can resolve these Firefox console warnings.
Thanks very much,
Josh
Beta Was this translation helpful? Give feedback.
All reactions