Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan Premium
Premium
Country
Ireland
Device
Mac
Operating System
macOS Big Sur
My Question or Issue
So i'm using the latest castlabs build of electron with widevine to get my web app leveraging the Spotify Web SDK to package up for desktop use. (because I can reliably get it to work outside of Chrome)
The player sets up, the device gets registered, my token is valid and capable of making calls to the wider API but as soon as track starts playing the playback state changes with that state suggesting that the track is done.
Interrogating the console suggests that while the SDK itself is functioning, has passed all the DRM checks etc etc when hitting the https://api.spotify.com/v1/widevine-license/v1/audio/license? endpoint, the API is spitting back a 500 internal server error.
I'm a little bit frustrated. This SDK has a dirt poor DX and every time I make progress and begin to move forward, i'm struck with another SDK issue or short coming and have to find a work around.
Now for the business case for taking this (and we, the devs) seriously:
Just like Spotify themselves, devs are always looking to push the industry forward, leveraging the tools at their disposal to create the next big thing. If Spotify continue to put up barriers to adopting their platform, devs will just go to the Apple Music SDK and build the next big thing on top of that instead. Being dev friendly is good for business.
Hey @RadicalApp, thanks for posting here!
Right now, the Web Playback SDK isn't supported for Electron. All supported web-browsers are listed on: https://developer.spotify.com/documentation/web-playback-sdk/#supported-browsers.
You might be able to find some tips and tricks for using Electron and the Web Playback SDK here: https://github.com/spotify/web-playback-sdk/issues/7
The right folks check in on the Developer boards occasionally and your feedback will be passed on to the relevant teams. If you have any other questions, feel free to post a new thread on the Spotify for Developers board.
Thanks, have a good one,
Hubo
We're running into a similar issue. Does anyone have any advice on how to fix? We've confirmed Widevine is working in our Electron app in development (we can play Widevine DRM content). We see the Spotify player connect because we get a device id. However, when we start playing we're seeing 500 errors from https://api.spotify.com/v1/widevine-license/v1/audio/license endpoint. Any ideas on how to fix this?
can say that Spotify's SDK is a useless one. no docs nothing. Mine gets assigned a client id, and shows up in Spotify connect, but this useless DRM thing is making songs skip every time.
Same here...waste two days try to figure it out
After a year, any progress or ideas can share? Thanks
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…