Hello, I am just getting familiar with the extension environment, but I ran into an issue regarding the client-sided listen function for the PubSub.
When I subscribe (listen) to the broadcast channel from the client-side I get an ERR_BADAUTH response from the SOCKET. At first I suspected this was because the extension had to finish authenticating before subscribing, so I put it on a 5 second timeout before starting to listen. But as soon as it starts it sends this over the socket:
So the BADAUTH error persisted. I verified and decoded the JWT from the same client in my EBS and there seemed nothing wrong:
{ exp: 1617196882, opaque_user_id: '<opaqueID>', role: 'viewer', pubsub_perms: { listen: [ 'broadcast', 'global' ] }, channel_id: '<channelID>', user_id: '<userID>', iat: 1617110482 }
So it definitely has the necessary listen permissions (that being broadcast), but it still does not work!
Keep in mind, this is all even before I even send my first message from the EBS, the issue lies in authenticating to the socket.
The code I use to listen:
...
setTimeout(() => {
twitch.listen('broadcast', function(topic, contentType, message) {
twitch.rig.log("listen() fired, received PubSub message: " + message)
});
}, 5000);
...
Where the timeout of course is temporary and just there to make sure this fires AFTER authentication.
