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

Required configuration segment prevents chat message and live activated channel endpoint #5

Open
Breci opened this issue Dec 6, 2019 · 3 comments
Labels
product: extensions ticketed Has been given an internal tracking ticket

Comments

@Breci
Copy link

Breci commented Dec 6, 2019

Brief description
When an extension has a required configuration segment, it can't send any chat message using the POST https://api.twitch.tv/extensions/<client ID>/<extension version>/channels/<channel ID>/chat endpoint
You get a 401 unauthorized as a response and the chat message isn't sent

It also prevents channels to be register and unregistered in GET https://api.twitch.tv/extensions/<client ID>/live_activated_channels endpoint . The activation also don't appear on the analytics
If someone installs the extension with a configuration segment required, the channel isn't returned to the list and not added to the activations in the extension analytics.
If someone uninstalls the extension on a version now has a required configurations segment, but installed it on a version that doesn't, they will still be returned by the live activated channel endpoint, even if they don't have the extension anymore

How to reproduce
See: https://discuss.dev.twitch.tv/t/bug-unable-to-send-chat-messages-when-configuration-service-segment-is-required/20286

Expected behavior
The chat message should be sent and an error 204 returned
The channels should be correctly tracked

Additional context or questions
Confirmed on the 17/07/19 on discord by Puglugger and crazyjack12

@mauerbac
Copy link

ticketed EXT-1160

@mauerbac mauerbac added the ticketed Has been given an internal tracking ticket label Mar 30, 2020
@lamai6
Copy link

lamai6 commented Sep 19, 2021

Unfortunately, this bug is still here even using the new Twitch API endpoint...

@p4dd9
Copy link

p4dd9 commented Jul 17, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: extensions ticketed Has been given an internal tracking ticket
Projects
None yet
Development

No branches or pull requests

4 participants