Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty user_name field in Get Followed Streams endpoint when channel first comes online #500

Closed
Wallboy opened this issue Sep 13, 2021 · 3 comments
Labels
product: api API endpoints in the "helix" namespace stopped investigating An issue that cannot be reproduced and is no longer being actively investigated.

Comments

@Wallboy
Copy link

Wallboy commented Sep 13, 2021

Brief description
When a channel first comes online, if you make a request to the Get Followed Streams endpoint, the user_name field will be an empty string for that channel.

How to reproduce
It's easy to reproduce:

Use a test account and follow yourself on another account. Go online on the test account and make a request to Get Followed Streams endpoint until the channel shows up. The user_name field will be an empty string. This problem persists when making the same request for roughly ~15-30 seconds until the problem fixes itself and the user_name will finally have the proper value.

Expected behavior
user_name field is not an empty string

Screenshots
Here is the JSON returned when the problem happens:

https://pastebin.com/KM5cF5Za

Additional context or questions
I noticed someone having a similar issue with the webhook that was posted nearly 3 years ago. I'm not sure if the problem is related.

@Wallboy Wallboy added the product: api API endpoints in the "helix" namespace label Sep 13, 2021
@bastimeyer
Copy link

Still not fixed. Both the user_name and tag_ids fields are empty/null.

Example response from a followed stream which has just come online:

{
	"id": "45250445197",
	"user_id": "26490481",
	"user_login": "summit1g",
	"user_name": "",
	"game_id": "138585",
	"game_name": "Hearthstone",
	"type": "live",
	"title": "chillin on hearth. !gfuel !merch - @summit1g",
	"viewer_count": 0,
	"started_at": "2022-01-22T23:15:17Z",
	"language": "en",
	"thumbnail_url": "https://static-cdn.jtvnw.net/previews-ttv/live_user_summit1g-{width}x{height}.jpg",
	"tag_ids": null,
	"is_mature": false
}

As a workaround, the users endpoint can be queried with the user_id, which is available (fortunately).

s4my added a commit to s4my/TwitchLiveChannels that referenced this issue Mar 24, 2022
the twitch API (twitchdev/issues#500),
which causes false positives in the notifications.
s4my added a commit to s4my/TwitchLiveChannels that referenced this issue Mar 24, 2022
the twitch API (twitchdev/issues#500),
which causes false positives in the notifications.
s4my added a commit to s4my/TwitchLiveChannels that referenced this issue Mar 24, 2022
the twitch API (twitchdev/issues#500),
which causes false positives in the notifications.
@Klemms
Copy link

Klemms commented Nov 10, 2022

Still an issue

@Xemdo
Copy link

Xemdo commented Aug 15, 2023

Unable to reproduce this when testing. Not sure if this is still an occurring issue.

@Xemdo Xemdo closed this as completed Nov 9, 2023
@Xemdo Xemdo added the stopped investigating An issue that cannot be reproduced and is no longer being actively investigated. label Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: api API endpoints in the "helix" namespace stopped investigating An issue that cannot be reproduced and is no longer being actively investigated.
Projects
None yet
Development

No branches or pull requests

4 participants