"Couldn't find that playlist" keeps happening when I click on the Daily Wellness playl

[setu1d]

I can confirm this happen on Linux as well, using the standalone client (spotify-client) or the same, packaged as a snap (snap install spotify).

I can search for a stock playlist, the playlists show up, and when I click on them, it will spin and spin for about a minute, and then return "Couldn't find that playlist".

Also, 90% of the existing playlist's songs are grayed out when using the standalone client;. There are no firewall restrictions blocking access to spotify, and the same workflow works fine in a desktop browser on the same machine. I can see the playlists, their songs, and those songs are not grayed out.

This appears to be exclusively restricted to the standalone desktop client not being able to parse the API responses coming back from Spotify itself.

[setu1d]

Replying back to myself.. I've just deleted the various ~/.cache/spotify and Index LevelDB files that are associated with the standalone Spotify client, with the same results. ALL of the playlists within Spotify , canned or custom, do not contain any songs when using the standalone client.

Watching the firewall and router logs, I see nothing at all being blocked from this client or related domains, and so can only surmise that the Electron client is out of date with whatever the current Spotify server-side requires for responses. This used to work until about a month ago when it stopped working.

Without a standalone client to use, separate from running it in a browser tab, there's really no compelling reason to continue my Premium account any further. I can use YouTube or Pandora and get the same results.

In this tight economy, I have to make difficult choices, and if Spotify no longer can provide the same level of function and service that encouraged me to subscribe, I will have to terminate that account and redirect those funds elsewhere.

I'm hoping this can be fixed before the end of the month, so I don't have to make that decision.

Update: Just confirmed this happens with ALL content in the standalone client, including podcasts and audiobooks. The client can pull the album or book cover/clipart, but when clicking on it to play it or view its details, it returns "Couldn't find that page".

A web browser on the same machine, using the same network + firewall rules/DNS, is able to find and play the content without issues, using the web player.