EventSub Channel Chat Message not showing Shared Chat

API
1

I’m trying to read chat through EventSub Channel Chat Message, which (as is my understanding) should include any and all messages that come into broadcaster_user_id’s chat, including anything coming through Shared Chat. I do see messages originating from the broadcaster’s chat; however, I’m not seeing Shared Chat messages coming in. The documentation doesn’t mention that I should be doing anything differently to get those, so as far as I know, I wouldn’t need any additional scope or subscription to see those with a user access token, just user:read:chat. Am I missing anything?

2

It’s working as expected for my recievers, the usual suspect here is either

  • just using guest star stream together and not shared chat
  • shared chat had (randomly) disconnected and the channels not sharing chats (but then you should of seen some messages before it popped)

There is also a third option, the account you are reading chat as, is banned from one of the other channels that chat is being shared with (and off hand I’m not sure what the expected behaviour is on eventsub’s side)

Testing my own implementation Eventsub is working as expected wrt to shared chat, here cdawg and caedrel are sharing chat and I’m connected to cdawg as the “home” chat.

Anything with an orange square is from not the source channel (example EventSub WebSockets Chat edition with Implicit Auth Example )

image
image1232×510 175 KB

Also check that the raw message ifsource_broadcaster_user_id is null/not null, and you are not misintrpreting the payload?

3

Shared Chat is definitely enabled, and I can see chat messages come through on other programs, so that more or less discounts all of those situations.

Otherwise, I feel like the most likely problem is implementation. I think the library I’m using (rust:twitch_highway) is relatively new, and so might not be properly picking up Shared Chat messages, though I’m not sure how (if even possible) to make the library output any sort of debug message to see if they’re coming through.

4

The developer of that library might be the place to start then. Unsure if they are present on the forums to catch and reply to this query.

5

After reviewing the library’s code myself, I’ve determined there may be a data parsing issue resulting in the packet getting quietly discarded. I’ve reported it to the author. My next Stream Together is on Sunday, so I won’t be able to determine whether the problem is fixed until then.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.