Cannot connect my spotify account

[Lenteguppie]

When I want to configure your Skill with my Spotify credentials I get an error page with the error: INVALID_CLIENT: Failed to get client. Am I doing something wrong?

[forslund]

Recently Spotify disabled the skill's API key so the skill can currently not be used. I'm trying to get through to Spotify to get this up and running again I'm also working on a workaround where users can supply their own key to the skill. got a POC on that but it'll require some more work to get it user friendly.

[Lenteguppie]

Ok, thanks! I am looking forward to it!

[fermulator]

same

The observation

Recently noticed:

 00:51:32.905 | INFO     |   712 | __main__:handle_utterance:72 | Utterance: ['play classical music on spotify']
 00:51:33.117 | INFO     |   706 | Playback Control Skill | Resolving Player for: classical music on spotify
Removing event mycroft-playback-control.mycroftai:PlayQueryTimeout
Removing event mycroft-playback-control.mycroftai:PlayQueryTimeout
Removing event mycroft-playback-control.mycroftai:PlayQueryTimeout
 00:51:40.423 | INFO     |   706 | Playback Control Skill | Playing with: mycroft-spotify.forslund
 00:51:40.696 | ERROR    |   706 | SpotifySkill | User info has been set but Auth failed.
 00:51:40.958 | INFO     |   706 | Playback Control Skill | Audio service status: {}

I confirmed my user/pass is correct in the config, so then retried the "Connect" button in the account skills
https://account.mycroft.ai/skills

it punts me to something like:
https://accounts.spotify.com/authorize?client_id=SNIP&redirect_uri=https%3A%2F%2Fapi.mycroft.ai%2Fv1%2Fauth%2Fcallback&scope=user-library-read+streaming+playlist-read-private+user-top-read+user-read-playback-state&state=SNIP&access_type=offline&response_type=code

browser shows: INVALID_CLIENT: Failed to get client

@forslund - per discussion;

System Versions

• mycroft-core 20.8.0

(.venv) pi@picroft:~/mycroft-core/skills/mycroft-spotify.forslund $ git status
On branch 20.02
Your branch is behind 'origin/20.02' by 1 commit, and can be fast-forwarded.

[fermulator]

What is a bit bonkers to me is:

1. Google and Alexa do this ... did their systems get blocked too?
2. https://developer.spotify.com/documentation/web-api/ specifically talks about how to achieve integration for develop "My App" ... hmmm

[fermulator]

Found:
https://developer.spotify.com/terms/

Do not use the Spotify Platform, Spotify Content, Spotify Service, or Spotify Marks in any way to create a voice-enabled SDA that enables a user to control with his or her voice, or any kind of voice assistant that provides voice-control functionality without prior written authorization from Spotify.

[fermulator]

This sucks 😢 , we will try to go through official spotify channels to get this resolved.

[Y0ngg4n]

@fermulator any Updates from Spotify?

[fermulator]

Nothing yet;

1. tried: https://developer.spotify.com/terms/#report-form-modal about a week ago
2. seeing if I can find a colleague their to learn more about the process

@forslund indicated to me offline he contacted them as well (not sure by which method)

The other way I know of is:
https://developer.spotify.com/support/

App Integration Application To build and distribute an application that using commercial integration, you must log in and create a client ID. You will be asked to fill in a form to submit an Application Integration Request.

But obviously this already went through that process? (@forslund can confirm) - but the application/request is so basic, I'm not sure how Spotify intends to approve or denote applications that REQUEST for written consent to have their application control Spotify via voice...

[Y0ngg4n]

Yes but same here with Deezer. Wrote them approximately 5 Emails and they sayed to me write them on twitter but no answer yet.

[forslund]

I started the "HW partner application" process, I also reached out through their Developer support (which I think is new) asking if there were some other channel to go through for this. They confirmed that it was the HW partner form that was needed. So it's the waiting game right now...

[Y0ngg4n]

@forslund ok thank you for your engagement ;)

[0vermind]

I fear only hardware partners with some kind of deal will be admitted. It is always a money game. Sad.
p.s. In the old days, fake the client's ID was the solution but I suppose that there is some kind of cryptographic keys involved now. We can't tell everybody we are "Alexa". :P

[forslund]

Yes that's my fear as well. There is a branch which can use user supplied auth info, but I still need to write some docs on how to use it and make it smoother in case Spotify declines again.

[Djinnxie]

i cant figure out how to use my own key. is there a guide anywhere?