Originally Posted by juiceme

OK, now it seems this situation is not anything temporary; as it is currently CuteSpot is not functioning correctly.

I checked the versions of the spotify android-sdk components in github; https://github.com/spotify/android-sdk and https://github.com/spotify/android-auth for recent changes.
The player library has not been updated for 2 years, and authorization library for 4 months.

Now, when starting harbour-cutespot from console I get the following console logs;

Code:

[nemo@Sailfish ~]$ harbour-cutespot 
[D] unknown:0 - Using Wayland-EGL
08:53:00.433 I [ap:1752] Connecting to AP ap.spotify.com:4070
08:53:00.599 I [ap:1226] Connected to AP: 104.199.64.158:4070
08:53:00.921 E [ap:3953] Connection error:  410
08:53:01.453 I [offline-mgr:2082] Storage has been cleaned

The http error message 410 means "Gone" as defined in RFC2616 and it means that "The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent."
This code is used when a resource or API has moved to new location and not used any longer.

Now it looks to me that Spotify has changed the web-API location and format and that's the reason the connection fails.