@Dist …
yes, you are correct.
After I deployed to actual Twitch hosting, the configuration service was able to set.
The developer rig is a bit janky. IMHO. Not sure how all of these developers are able to figure out these quirks without trial and error.
Side question: Maybe you know the answer to this…
I am able to see the extension that I am developing and installed on my own account. That works fine.
I created a secondary test Twitch account and I invited that user via theTwitch Access > Testing Account Allowlist to provide access to this extension during testing.
I did this because I want to see how the extension would look for another random user who is visiting my channels about page…
In summary:
How can I test the extension from an anoynmous or logged in Twitch user (other then myself) when they visit for example twitch.tv/myusername/about
Currently: I can see the panel working great on my own account.
However, when I try to browse as an anonymous non-logged in or another logged-in user, I don’t see the panel at all showing.
Any ideas? Does it only show once the extension is actually published? If so what is the best way to test?