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

[Bug] Using verify-subscription channel.follow requires version param #288

Closed
dynamitejustice opened this issue Oct 22, 2023 · 1 comment · Fixed by #296
Closed

[Bug] Using verify-subscription channel.follow requires version param #288

dynamitejustice opened this issue Oct 22, 2023 · 1 comment · Fixed by #296

Comments

@dynamitejustice
Copy link

dynamitejustice commented Oct 22, 2023

What is the problem?

When attempting to perform the command twitch event verify-subscription channel.follow the reponse says that the version is invalid and requires 1,2. This makes sense as when you attempt to just do a event trigger for follow I add --version 2 at the end and it works fine. I'm unable to add --version 2 or even 1 anywhere within the call for it to specify the version needed and perform the verify-subscription action. I have tried moving the --version 2 param around in case it was an order of operations thing but no luck.

Operating System

Windows 10

Architecture Version (x86, x64, arm, etc)

x64

Steps to reproduce

  1. Perform the following command twitch event verify-subscription channel.follow -F https://[redacted]/callback -s [redacted] --version 2
  2. Note the response of Invalid version given. Valid version(s): 1, 2 Use --version to specify

Relevant log output

No response

@Xemdo
Copy link
Contributor

Xemdo commented Nov 28, 2023

Should be solved for channel.follow by #290 because it reduces it down to just one version, but that doesn't solve the underlying issue. I'll try to add in a fix before the next release to avoid future issues.

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

Successfully merging a pull request may close this issue.

2 participants