Hi Barry! Thank you for your patience.
Alright, so if what I told you before does make sense then I have another question before moving on.
When I started developing my extension, the developer-rig was on the first versions. I clone the repository and got the new rig-version. I did some changes on the .env.local file, specifically on the EXT_CHANNEL property and what I noticed is that the onAuth() function is still returning the “old” EXT_CHANNEL name. I read the readme.html in case that I’m missing something and there was a lot of new things to configure. I’ve always used the yarn start command to start the dev-rig. My front-end extension and the back-end are hosted on a local IIS. If I change something on any of them the changes are indeed updated. So my question now is: is this still the way to start the dev-rig?
My question comes because window.Twitch.ext.listen() isn’t getting triggered. What I did was to open the dev-rig, run a unit test on my EBS to post to the PubSub and I was hoping to ext.listen() to receive the message I’m sending. But I’m not sure if this is how it’s intended to work and if PubSub works when testing locally.
Thank you again for helping me out!