-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
set_session not working #324
Comments
same, also it makes it unable to authenticate on lot of functions |
Just realizing I can't do this. dying |
I'm not fully understanding the reproduction steps, can you please provide an example repo with this issue for me to take a look at? |
You need to provide the refresh token of the session to set the session. (I don't know why the refresh token is needed but it works)
|
Closing this out as there has been no activity on this issue from OP over a month now. |
Tracing through the code because I hit this as well. I was able to work around this by setting
I think this should be a one-line fix to remove the conditional, will give it a shot |
PR here: #610 |
Describe the bug
My understanding is that
set_session
should take in a jwt, and set the session on the supabase client, but when I callset_session
with a valid access token, and then right after callget_session
, I get back None.To Reproduce
Sidenote: I'm currently using the
custom_decode_jwt_payload
as a workaround for supabase/supabase-py#395.Expected behavior
Return the new session, and the supabase client can access protected resources.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: