-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still having getSession warning whenever _saveSession is called #912
Comments
Have you heard back about this? |
@larbish, you got any news about this issue? |
No news about it so far... @thorwebdev could someone have a check at this please? I'd love to merge my PR in the module and use |
We'll check this as soon as we can. Any external help in tracking down where the use comes from would help speed it up. |
Looks like the code calls |
I am seeing this constantly right now ever since updating to SSR 0.4.0 and following the documentation. Going back to SSR 0.3.0 this seems to git rid of the messages. |
Bug report
Describe the bug
Maintainer of the nuxt/supabase module here.
We have a PR to migrate on the@supabase/ssr
package and we're still experiencing this issue with the latest released version including your PR.The module is now using the
@supabase/ssr
package and we're still experiencing this issue with the latest released version.I've removed all occurrences of getSession() in the module and I still have the warning.
Any help on this would be appreciate 🙏
To Reproduce
Clone the nuxt/supabase repository and follow the development readme to run the playground.
Notice the
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure
warning.Expected behavior
Do not display this warning.
The text was updated successfully, but these errors were encountered: