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

Pubsub channel subscription scope has changed #342

Closed
aetaric opened this issue Mar 26, 2022 · 1 comment · Fixed by #343
Closed

Pubsub channel subscription scope has changed #342

aetaric opened this issue Mar 26, 2022 · 1 comment · Fixed by #343
Labels
Milestone

Comments

@aetaric
Copy link

aetaric commented Mar 26, 2022

Bug Report

We (Twitch) have changed the pubsub scope for channel-subscribe-events-v1.<channel ID> from channel_subscriptions to channel:read:subscriptions. Twurple fails on a token with this scope. The current scope requirements for topics can be found here: https://dev.twitch.tv/docs/pubsub#topics

Code

literally any code implementing pubsub for subscriptions

Expected behavior

pubsub connection works

Actual Behavior

The following output is from nodecg-io-twitch-pubsub:

[2022-03-26T00:27:30.565Z] ❌ twurple:pubsub ERROR Retrieving an access token failed: This token does not have the requested scopes (channel_subscriptions) and can not be upgraded.
If you need dynamically upgrading scopes, please implement the AuthProvider interface accordingly:

        https://twurple.js.org/reference/auth/interfaces/AuthProvider.html
[2022-03-26T00:27:30.566Z] ⚠️  twurple:pubsub WARNING No valid token available; trying to refresh

Environment

  • Version: 5.0.18
  • Node version: v16.14.2
  • Operating system: All
@aetaric aetaric added the bug label Mar 26, 2022
@iProdigy
Copy link
Contributor

could just change to the new scope name here and/or this logic could be updated to accept equivalencies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants