mirror of
https://github.com/sigma67/ytmusicapi.git
synced 2026-04-26 07:46:00 +03:00
[GH-ISSUE #330] YTMusic.get_album_browse_id raising KeyError: 'header' #257
Labels
No labels
a/b
bug
documentation
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
yt-error
yt-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ytmusicapi#257
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @natumbri on GitHub (Dec 22, 2022).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/330
Hi,
When using an authenticated ytmusic client,
ytmusic.get_album_browse_id(id)is causingnavto throw aKeyError: 'header'for me (example response here: https://gist.github.com/natumbri/b82b3c3b6933b8c861eab92e3c32f30f). The other methods work just fine with the authenticated ytmusic client.No problem with an unauthenticated client:
YTMusic.get_album_browse_id(YTMusic(),id)works just fine (example response here: https://gist.github.com/natumbri/12c6fe0313cfa49294268fd7982d3a1c)Seems to happen for all ids, but definitely with this one
OLAK5uy_lUNm1YMm972Rvy0LpDg3ORQFjtN_8oBtc.Cheers,
Nik
@sigma67 commented on GitHub (Jan 1, 2023):
That's strange, I don't have this issue with my account. Have you checked that you're able to access the album in your browser?
https://music.youtube.com/playlist?list=OLAK5uy_lUNm1YMm972Rvy0LpDg3ORQFjtN_8oBtc
@natumbri commented on GitHub (Jan 1, 2023):
Yeah, it is odd. The url works fine in my browser, when logged in.
I'm pretty sure this previously worked just fine for me, too.
I'll continue to try to work out what happened....
@sigma67 commented on GitHub (Jan 27, 2023):
Did you run into this issue again or manage to find a root cause? Else I'd go ahead and close this due to lack of reproduceability.
@natumbri commented on GitHub (Jan 27, 2023):
To be honest, I haven't looked into it. Go ahead and close; if I run into it again, I can reopen.
Cheers
Nik