Spotify API Error

[eximo84]

Describe the bug
I haven't configured spotify but all my imports are failing to tag due to the below error

Expected behavior
Files to be tagged via Music Brainz

To Reproduce

Add file to folder, wait for tag to fail

Technical Details

Spotify authorization failed: 400 Client Error: Bad Request for url: https://accounts.spotify.com/api/token {"error":"invalid_client","error_description":"Invalid client"}

[recursivepaws]

i'm experiencing the same thing

[pSpitzner]

Indeed, this should not be happening.
Can you double-check that the spotify plugin is not in your list of plugins, in neither of your configs?

As a workaround, you can set the spotify client id and secret.
Presumably, beets had to change them a few weeks back because spotify reacted to the recent data archival project.

Here you can find the new credentials, until we update our beets dependency.

Place them in your beets/config.yaml like this (see the spotify plugin docs for more details):

# beets/config.yaml
spotify:
    client_id: REDACTED
    client_secret: REDACTED

[GithubEnjoye]

Does this fix work for anyone? I tried it but I am still geting the "Spotify authorization failed: 400 Client Error"

[semohr]

Worked for me :) Have you restarted the container?

[GithubEnjoye]

Yes, I did restart it. I understand you use the default (original) JSON token with the updated client_id and client_secret? Or do you have a private JSON from before the hold on creating tokens on developer.spotify.com?

[semohr]

I think you need to delete the json token.

[Rom0067]

Hello all. I was wondering if I am able to use my own Spotify client id and secret? I know they are making changes and I do have a premium account (for now) but when I tried using my creds in the config I was getting tagging failed errors. As soon as I put the above creds in the config, deleted the json file, and restarted beets worked fine. Any advice is greatly appreciated. Thanks!

[pSpitzner]

Hey @Rom0067,

yes, you should totally be able to use your own credentials.

Have you checked that you enabled sufficient permissions for your app in the spotify developer portal?
(To be sure, I'd grant all, from the top of my head not 100% sure which ones beets needs.)

[Rom0067]

Thank you for the reply! I have to be honest I'm not sure what you mean by permissions. I logged back into the dev portal and I can't find anything about permissions. I'm actually kinda confused about the overall setup (I know this isn't your problem) as I had an app working fine for about a year. Spotify is changing things and it broke a lot for me. I'm wondering if maybe I have the improper redirect uri as they no longer allow http://localhost. Back to the point though I can not get beets to work with my creds anymore it's frustrating. Sorry for the rant. You are great and always very helpful btw I love your app!

[pSpitzner]

I was talking about the permission scopes, but realized that for spotify, they are set when making the auth request (i.e. beets does that). So they are not baked into your client_id, as I had thought.

But you are right, Spotify is making changes, and invalidated some existing apps (like beets). Note that I cant create any new apps at the moment, too.

In any case, why do you want to use your own credentials?
The ones I referenced above from the newer beets version work fine on my setup.

best,
p

[Rom0067]

Sorry for the late reply. I am only using my own creds because I thought I had to. If using the keys you provided works then I will continue using those. If something happens and those keys change where can I find new ones? The official beets docs? Thanks for all the information!

[pSpitzner]

Nah, no need for your own credentials :)

The only reason this comes up at all is because spotify broke/disabled a bunch of credentials recently.
Beets updated theirs, but we have not updated beets yet.