Skip to content
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

Missing await on 'realtime.set_auth' for async client. #919

Closed
LuisLechugaRuiz opened this issue Sep 3, 2024 · 1 comment · Fixed by #918
Closed

Missing await on 'realtime.set_auth' for async client. #919

LuisLechugaRuiz opened this issue Sep 3, 2024 · 1 comment · Fixed by #918
Assignees
Labels
bug Something isn't working

Comments

@LuisLechugaRuiz
Copy link

LuisLechugaRuiz commented Sep 3, 2024

Bug report

  • [ - ] I confirm this is a bug with Supabase, not with my own application.
  • [ - ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Async client is broken due to a missing 'await' at self.realtime.set_auth()

To Reproduce

Initialize async client and propagate a Auth event.

Expected behavior

Auth event triggers supabase real time which push the content over websocket asynchronously.

Solution

@silentworks
Copy link
Contributor

This is an issue that needs to be resolved but I don't think this is the approach to solving this. The realtime client should follow the other client libraries and take in a header property on initialization and that header should be updated each time an auth event happens.

@silentworks silentworks self-assigned this Sep 10, 2024
@silentworks silentworks linked a pull request Sep 28, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants