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

Realtime: Better error message when providing incorrect token #53

Closed
inian opened this issue Sep 27, 2020 · 0 comments
Closed

Realtime: Better error message when providing incorrect token #53

inian opened this issue Sep 27, 2020 · 0 comments
Assignees

Comments

@inian
Copy link
Member

inian commented Sep 27, 2020

Bug report

Describe the bug

I get the following error message when not providing an auth token or giving an incorrect token. The error message should say something like incorrect (or missing) token instead of Network timeout.

wss://xxx.supabase.co/realtime/v1: REALTIME DISCONNECTED
wss://xxx.supabase.co/realtime/v1: REALTIME DISCONNECTED
wss://xxx.supabase.co/realtime/v1: REALTIME DISCONNECTED
wss://xxx.supabase.co/realtime/v1: Network timeout. Still waiting...

To Reproduce

const { createClient } = require("@supabase/supabase-js/lib/index");
const supabase = createClient(SUPABASE_URL, "incorrect token");
// or const supabase = createClient(SUPABASE_URL, null);

supabase
  .from("table")
  .on("*", (payload) => {
    console.log("Change received!", payload);
  })
  .subscribe();
@kiwicopple kiwicopple self-assigned this Sep 30, 2020
@kiwicopple kiwicopple transferred this issue from supabase/supabase-js Oct 15, 2020
kiwicopple added a commit to supabase/supabase-js that referenced this issue Nov 2, 2020

- Fixes #32 Major DX change: response and error handling
- Fixes #49 When no `supabaseKey` is passed in it throws an error
- Fixes #31 chore: set up semantic releases
- Fixes #15 `supabase.auth.logout()` throws "Invalid user" error.
- Fixes #20 Auth: Change DX of user management
- Fixes #30 Supabase auth interface missing informiation
- Fixes supabase/supabase#147 supabase/supabase#147
- Partial fix for supabase/realtime-js#53  - if there is no token provided. The error needs to be caught at a socket level.
- Adds magic links


## BREAKING CHANGES

- See all breaking changes in RELEASE.md v1.0.0
- Errors are now returned and not thrown
- Auth now uses `@supabase/gotrue-js` interface
- `supabase.getSubscriptions()` only returns open subscriptions



* Updates the config

* chore: Migrates the basic outline to TS

* Adds a simple example showing how it can be used.

* chore: Moves tests to jest

* chore: Adds semantic releases

* Moves the subscription into it's own class

* Updates the todo readme with simple instructions

* Updates installs

* Revverts commented code - sorry for the spam

* docs: adds JSDoc to some functions

* chore: Adds a function for backwards compat

* chore: migrates the client to SupabaseClient

* This change attempts to make the naming conventions the same as Thor's previously

* Updates GoTrue to latest version

* Adds generic type to the from, and updates the name of the query builder

* Updates to latest versions of all packages

* Updates the example to make sure it's working

* Refactor SupabaseQueryBuilder

* Adds prettier hook

* Add TypeScript next.js example.

* Declutter SupabaseClient and make work with gotrue-js changes.

* Bumps the GoTrue version

* Bumps postgrest to include the types

* Temporarily adds the spec so that I can use it in our docs

* Update examples and add resetPassword.

* Bump gotrue-js version.

* Update lockfile.

* Add auth magic link capabilities.

* Gotrue-js user and session method updates.

* chore: Adds release notes

Co-authored-by: Thorsten Schaeff <[email protected]>
Co-authored-by: Thor 雷神 Schaeff <[email protected]>
@w3b6x9 w3b6x9 closed this as completed Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants