Failed to start pusher: No client id specified about multistreamer

[jprjr]

Hey sorry, you're right I haven't had too much time but I'll try to look into it now that I've got a break from work for the winter holidays.

[k1ck3r]

have the same issue only with twitch, and i suppose your issue is same.

[pogzie]

I tried un-associating the accounts and re-associating but it didnt work. For the sake of "fixing" it faster, I created a virtual machine image of a fresh install.

[k1ck3r]

actually if you re-authenticate twitch, everything is back to normal. already gave full explanattion in my opened issues regarding twitch authentication module. but seems Jp don't have enough time to look into it

[jprjr]

Identified the likely culprit - at some point, Twitch added expiration times to newly-generated tokens, which is why my installation never noticed this problem. Older tokens never expire!

I'll have to write up token-refreshing code, similar to what the YouTube module does.

[pogzie]

Thanks good sir! Let us know if you have a new build so we can update!

[jprjr]

I've pushed 2 new branches - fix-twitch and fix-twitch-legacy, that should have the token-refreshing fix.

I say "should" because I just wrote it, and haven't had a token expire just yet for me to test the refresh, which is why it isn't in master. If anybody wants to try those branches out, feel free! I'll hopefully be confirming everything works and merging into master later tonight or tomorrow morning.

[jprjr]

Just confirmed the token refresh works as it should - I've released version 11.0.3, and I backported the fix to version 10.2.7 (in case you haven't updated to 11 yet)

[tvvignesh]

@jprjr Looks like the docker version does not have the fix yet. I am encountering the same issue. Just downloaded the repo a week ago.