mirror of
https://github.com/sigma67/ytmusicapi.git
synced 2026-04-25 07:16:00 +03:00
[GH-ISSUE #834] Unable to access playlists #515
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#515
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 @The-Lazybone on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/834
Describe the bug
ytmusicapi fails to parse playlist data for collaborative and public playlists, causing the script to crash when calling
get_playlist()with the error:"Unable to find 'text' using path ['facepile', 'avatarStackViewModel', 'text', 'content']".ytmusicapi version
1.11.1
Python version
3.13.9
To Reproduce
Steps to reproduce the behavior:
ytmusic.get_playlist(playlist_id)Full Error Messages
Error 1: Collaborative Playlist Parsing Error
Error 2: General Playlist Access Error
Additional context
The issue appears to be related to how YouTube Music structures collaborative playlist data. The response includes a
facepilesection with avatar information, but thetextfield underfacepile -> avatarStackViewModel -> text -> contentis missing, causing the parsing to fail.This suggests that YouTube Music has updated their API structure for collaborative playlists, and the ytmusicapi library needs to be updated to handle this new structure or provide fallback parsing for when the expected field is not present.
Error occurs with:
@czifumasa commented on GitHub (Nov 21, 2025):
Looks like duplicate of already fixed problem, that has not been released yet: https://github.com/sigma67/ytmusicapi/issues/820
@sigma67 When can we expect a new release?
@sigma67 commented on GitHub (Nov 24, 2025):
1.11.2 created, thanks for the ping