Given you never came back to your I thought you had got it working
If the extension doesn’t work, becuase your config setting code doesn’t work.
Then the extension doesn’t work, so it can’t pass review
Yeah a requirement for the config service is to have enabled it in the dev console
This is under Capabilities (greyed out as this is a screenshot from a released extension)
Review will “use the extension” under “hosted test” but force installed to one of the review channels. (Force as in bypassing any allow list restrictions).
So they are testing it on one of their own channels.
So to test, try installing to a new test channel, or clean back all the config variabels to empty/invalid and (re)install your extension and test the setup.
The Config service can be quicky in the Developer rig when using the helper to set. Personally I rarely test using the rig since I have a custom rig, behind a reverse SSH tunnel (think NGROK but without restrictions) so my live extension server handles SSL. So I can test to the Twitch Website insteasd of dealing with quirks in the rig.
I wrote a little about it on Part 5 on my Extensions Series Twitch Extensions Part 5 – Dev Environment – Barry Carlyon and my “rig” that handles compilation and serving code is on GitHub twitch_extension_blog_series/part_5/extension/extension at main · BarryCarlyon/twitch_extension_blog_series · GitHub
So I avoid the rig but serving my extension over SSL and then testing on the Twitch website, I generally avoid the rig since rig doesn’t do “what happens when a user becomes logged out of the extension to logged in” aka State Changes.
But if you are using the Config API to set config then you should avoid the quirks of the dev rig.
But you’ll probably find that if you are using the rig, you have the frontend view and config view set to different broadcasters, great for spot testing, but I wouldn’t use the rig for any actual config setting.
You can also look at adding an
onError callback to log any errors that get returned
Or whip out inspector and trace the calls in the network tab and check its doing what you think it’s doing.
And short of being in fron of your machine to look at what your setup is and how it’s interacting with your code it’s tought to debug this.
Especially since if you gave me your code I predict it would just work on my machine.