#When calling emote set updates, hangs on emote set that doesn't exist.

1 messages · Page 1 of 1 (latest)

void olive
#

I have encountered an issue while working with the Streamer.bot team. The issue pertains to a specific call made for my Twitch account via your SSE server to pull updated emote sets.

Here are the Streamer.bot logs for reference:

[2024-03-04 14:49:13.946 INF] 7TV :: Retrying EventStream Connection
[2024-03-04 14:49:13.946 INF] 7TV EventStream :: Connecting to 7TV EventStream, monitoring for changes on emote set 65e4ac8580346e1cb843ea6d
[2024-03-04 14:49:18.948 DBG] ServerSentEventsClient :: Unable to connect to SSE server within a reasonable time frame
[2024-03-04 14:49:18.948 INF] 7TV :: EventStream Disconnected
[2024-03-04 14:49:18.948 INF] 7TV :: Retrying EventStream connection in 120s

Explored possibilities this is on Streamer.bot side. The call made is correct and returns the expected data for every account tested. Streamer.bot will enhance their connection to timeout more quickly, as a stop-gap.

However, the problem persists. It appears that a rogue emote set, which does not exist, is trying to pull data from the emote set update, but doesn't show when polling the sets listed on my account. I have tried removing all of my emote sets and restarting with a fresh Streamer.bot app, but to no avail. Running manual calls in the browser also does not return that emote set id.

My account's details when polled from 7tv: https://7tv.io/v3/users/twitch/47846641. The data returned from this call appears as expected. However, while updating all my emote sets, it references an emote set that doesn't exist, 65cffe725ba65ab8f39c8b24.

When making a browser call to the ‘bad’ emote set https://events.7tv.io/v3@emote_set.update<object_id=65cffe725ba65ab8f39c8b24>, it returns an expected result as any other emote set.

Can someone help me look into why my specific user account is returning a rogue emote set that doesn't exist when trying to get emote set updates?

NOTE It DOES update my real emote set by the way, but hangs when it gets to the rogue one.