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

M_UNKNOWN_TOKEN should be reported in a friendly way. #23

Open
reivilibre opened this issue Jan 20, 2021 · 0 comments
Open

M_UNKNOWN_TOKEN should be reported in a friendly way. #23

reivilibre opened this issue Jan 20, 2021 · 0 comments

Comments

@reivilibre
Copy link
Contributor

Currently, if a dodgy access token is given, then this mouthful is spat at the user:

Error occurred during test: VoIPTesterError: M_UNKNOWN_TOKEN Invalid macaroon passed. undefined [Can't get TURN credentials from homeserver]

It would be nice to nicen this up — M_UNKNOWN_TOKEN seems like it should be the right thing to match against; I'm confident the spec will agree with that.

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

1 participant