Not getting song information

[Twelve0001]

Description

I've made sure my cookie is correct.

Steps to reproduce (omit if unpredictable)

Do what the readme says to do.

Environment

Windows, Opera GX

Confirmation

• I have searched for existing issues
• I use the latest version of LyricsStatus

[ZeldrisDarkRose]

Seems like the issue appeard today, I was using it in the morning without problem, and with the day going on the script broke

[RamenFighter03]

Posting to confirm this on my end too

[OvalQuilter]

Hi! Thank you for informing. I will check this when I get access to my computer.

[RamenFighter03]

Hi! Thank you for informing. I will check this when I get access to my computer.

Hi Oval, want to thank you again for all the hard work you’ve put down, this wouldn’t be possible without you. Let us know if you need any testing done on our side.
Btw, you should consider opening a discord server!

[OvalQuilter]

Hi! Thank you for informing. I will check this when I get access to my computer.

Hi Oval, want to thank you again for all the hard work you’ve put down, this wouldn’t be possible without you. Let us know if you need any testing done on our side. Btw, you should consider opening a discord server!

Thank you for the kind words, I appreciate it! It's really heartwarming for me that you and the others found my tool useful and liked it!

About the Discord server, it's a good idea, but I think LyricsStatus is not enough popular for this kind of interaction. For the more comforting communication between each other—absolutely, but otherwise it will be dead server most of the time.

[Azuralolx3]

hey just here to say im also experiencing this issue playing music on spotify yet it dosnt pick up in cmd i checked my cookies and even reentered them but nothing works

[OvalQuilter]

So I investigated it.

They changed the player interaction API in the web player, that's not the main reason, but concerning.

The main thing is, they're shadowbanning (or some sort of) attempts of getting playback state (song name, duration, etc). Though I can't completely confirm it, the authentication system (the process of getting an access token) seems to work fine, but the player API is refusing to accept credentials, throwing a 404 error. BUT when no credentials are provided it throws a 400 error and a message "No access token provided" which is ridiculous.

In short words, there's no solution for me yet, or at least in the short term. As they no longer use the player API in the web player, I have no clue of how to bypass this 404 error.

I can switch to the OAuth2, which requires creating an app on Spotify, but this means I need to change most of my code infrastructure to use this feature. I'm not saying it's hard, but it's time-consuming.

Update: they're hardcoded the process of retrieving parts of the playback state into multiple API calls, which is complicated as hell.

[Twelve0001]

So I investigated it.

They changed the player interaction API in the web player, that's not the main reason, but concerning.

The main thing is, they're shadowbanning (or some sort of) attempts of getting playback state (song name, duration, etc). Though I can't completely confirm it, the authentication system (the process of getting an access token) seems to work fine, but the player API is refusing to accept credentials, throwing a 404 error. BUT when no credentials are provided it throws a 400 error and a message "No access token provided" which is ridiculous.

In short words, there's no solution for me yet, or at least in the short term. As they no longer use the player API in the web player, I have no clue of how to bypass this 404 error.

I can switch to the OAuth2, which requires creating an app on Spotify, but this means I need to change most of my code infrastructure to use this feature. I'm not saying it's hard, but it's time-consuming.

Update: they're hardcoded the process of retrieving parts of the playback state into multiple API calls, which is complicated as hell.

does this mean V1 won't work as well

[OvalQuilter]

So I investigated it.
They changed the player interaction API in the web player, that's not the main reason, but concerning.
The main thing is, they're shadowbanning (or some sort of) attempts of getting playback state (song name, duration, etc). Though I can't completely confirm it, the authentication system (the process of getting an access token) seems to work fine, but the player API is refusing to accept credentials, throwing a 404 error. BUT when no credentials are provided it throws a 400 error and a message "No access token provided" which is ridiculous.
In short words, there's no solution for me yet, or at least in the short term. As they no longer use the player API in the web player, I have no clue of how to bypass this 404 error.
I can switch to the OAuth2, which requires creating an app on Spotify, but this means I need to change most of my code infrastructure to use this feature. I'm not saying it's hard, but it's time-consuming.
Update: they're hardcoded the process of retrieving parts of the playback state into multiple API calls, which is complicated as hell.

does this mean V1 won't work as well

Yes

[OvalQuilter]

Woops, miss clicked