Set Extension Required Configuration - stopped working for versions in local/hosted test

[BarryCarlyon]

Brief description

https://dev.twitch.tv/docs/api/reference/#set-extension-required-configuration

Response with "Sorry, you're not allowed to do that" for versions in local or hosted test

How to reproduce

• have an extension version that is not released that needs a configuration string to be set before activation
• try to set that string

Expected behavior

accepted and extension can be activated

Screenshots

Additional context or questions

I believe this broke due to changes yesterday

Initial report: https://discord.com/channels/504015559252377601/523676096277905419/1194685221212258524

[chris-lu]

Any feedback, workaround or ETA on this? It seems it's still now working, making the whole "Required Configuration" feature useless as new extension cannot be validated.

[beheh]

Just to add our voice, we're also affected by this and cannot submit a version with this anymore as we never get past the "Requires Configuration" state in the broadcaster dashboard.

What's even worse, migrating to the Extension Configuration Service is also problematic as to my knowledge the extension will be deactivated for all existing broadcasters. So it seems our only recourse is now to temporarily stop requiring configuration, start writing to the Configuration Segment for broadcasters, and then start requiring it again in a few months.

[jbulava]

This issue has been ticketed internally as ANC-3204 for investigation. More details to follow.

[jbulava]

A fix for this issue has been deployed today.