-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
failed to get_session after create_client by accees_token as supabase_key #663
Comments
This isn't correct as we introduced this before 2.3.3. Also the reproducible steps you've provided isn't complete. Please create a full reproducible example as its really hard to debug with partials. Also note I have 2.3.3 running in multiple demos. The quoted functionality has been there since 2.2.0 https://github.com/supabase-community/supabase-py/blob/v2.2.0/supabase/_async/client.py#L94-L103 |
Also note |
sorry to bother u ! i think i am too sleepy yesterday that misundertand the version🌹 Also there's no description in web doc about and can only pass access_token to if we can achive that,then could we |
@Atticuszz these are very good ideas, I'm going to add them to the list of things to get done and add them in when I get a chance or you can create a PR if you wish and I'll get them reviewed. |
This PR should have resolved this issue #766. |
Closing this out as I believe it has been resolved. |
Describe the bug
session = await client.auth.get_session()
,session got None unless i signed in with password etcin short ,it should be able to recognize the access token from front_end after signed in , create_client with the access token as supabase_key should work for it
To Reproduce
just called
add break point at
client._auth_token = await client._get_token_header()
you will find that client._auth_token set to None!!!,which means the
@property def postgrest(self):
can not be inited correctly byaccess_token
client._auth_token = await client._get_token_header()
the first time after called
get_session()
should return the correct session likeclient.auth.get_user(jwt)
,it worksDesktop (please complete the following information):
The text was updated successfully, but these errors were encountered: