a config set would normally be done in response to the broadcaster clicking a button to save config.
so you’d have to have passed onAuth in order for the extension to be visible.
as if an extension doesn’t onAuth Tiwtch tends to hide the iFrame all together and throw a suitable “extension not loaded (clientID)” console log (I forget the specific wording)
a script with a src tag or a script with JS
Inline JS won’t work on hosted test/release. So would be wise to emulate that in local test to ensuire you test environment matches production.
Not sure why you are referencing a secret, secrets should never be in the frontend/visible to the end user.
if you didn’t get an onAuthorized then things are not ready to go.
onAuthorized is similar to document.onload so you know that everything is loaded.
If you are not getting an onAuthorized, you are actually loading/testing this on a Twitch Page and not direct loading your HTML?
Additionally if you are utilising hot reload, that will prevent the Twitch Extension helper operating correctly