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
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 sentIt 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 anymoreHow 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