Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan
Premium
Country
US
Device
Occurs on both a custom desktop and a Lenovo Thinkpad T490
Operating System
Arch Linux 5.5.7-1-MANJARO
My Question or Issue
When I try to add a song to a playlist shared with me on the web app, it fails (with no visible error except in developer tools):
Spotify sends a POST request to:
https://api.spotify.com/v1/playlists/<playlist_id>/tracks
Payload: {"uris":["spotify:track:<track_id>"]}
The Forbidden response:
{"error":{"status":403,"message":"You cannot add tracks to a playlist you don't own."}}
Adding the same tracks to the same shared playlist on the desktop app works fine. Your permissions are not evaluating correctly on the web app. Are you using different API versions between the web app and the desktop app?
There's 100% a bug here. And it would be nice if the UX indicated that some kind of error occurred. It's strange that the UX decision was to give no feedback about a failure when a user makes a request that the Spotify app fails to fulfill.
-------
I'd like to add that it's SUPER frustrating to have to try to submit this 5 times and fill out the reCAPTCHA over and over (thanks for helping Google farm data from everyone by using their garbage) because you won't accept the topic labels.
For that label selector - if you have a finite list of label options, there's this thing called a DROP DOWN that can communicate that to users. There's this other thing called a MULTI SELECT that lets users choose more than one. I'm not surprised that the UX is about as intuitive here as in the app.