-
Notifications
You must be signed in to change notification settings - Fork 58
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
Malformed playlist field leads to confusing 'total' error #31
Comments
I had the same issue. I fixed it by changing the uri field from this fromat |
Agree; that's the way to format the URI. The issue @emallove is raising is that the error message is unhelpful for users trying to resolve the error (i.e., there's nothing to indicate that the URI was incorrectly formatted, the issue could be anything). |
Also just found this out after 10+ years of being a Spotify user: When you right click on a playlist in the desktop app and navigate your cursor to the "share" menu item, if you have the option butten held down, instead of copying the URL to the playlist, you can instead copy the Spotify URI. |
Thanks :)
Am So., 29. Okt. 2023 um 23:58 Uhr schrieb larra ***@***.***>:
… Also just found this out after 10+ years of being a Spotify user: *When
you right click on a playlist in the desktop app and navigate your cursor
to the "share" menu item, if you have the option butten held down, instead
of copying the URL to the playlist, you can instead copy the Spotify URI.*
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY5BLRLF2WUJSU5PMOPWULYB3NQZAVCNFSM5V53L322U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZYGQZDKNJZGEZQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
The playlist URI field must be in
spotify:playlist:<ID>
format, e.g., the below HTTP URL format will not work:But the error message caused by the malformed playlist field is confusing (red div with the text 'total'):
The text was updated successfully, but these errors were encountered: