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...
Receiving the following error when trying to initialize the Web Playback SDK on the latest Android Chrome versions (111 and 112). The player connects but fails to become 'ready'.
Uncaught (in promise) EMEError: No supported keysystem was found.
at new t (index.js:3:325353)
at t.fatal (index.js:3:325603)
at index.js:3:182297
This appears to be an issue with EME, although the latest Android Chrome seems to support it.
Is there something that needs to change within the SDK logic then?
Thanks in advance.
Plan
Premium
Country
US
Device
Pixel 5, Samsung S21
Operating System
Android Chrome 111, Android Chrome 112
Im having the same problem, have you solved it?
nope, I assume it's an SDK issue Spotify will need to address. Because other mobile browsers work fine
Maybe I'm getting same recent year.
Coming, 'PlaybackError'
I have the same problem but narrowed down the issue (at least with a desktop Chrome browser) to iframes with desktop Chrome.
If I run the same app of mine in a separate browser tab or window the problem goes away.
```
index.js:3 Uncaught (in promise) EMEError: No supported keysystem was found.
at new t (index.js:3:311054)
at t.fatal (index.js:3:311304)
at index.js:3:167541
**bleep**:3
**bleep**:3
(anonymous) @ index.js:3
Promise.then (async)
**bleep**:33
**bleep**:33
**bleep**:33
**bleep**:33
**bleep**:33
**bleep**:50
**bleep**:50
**bleep**:50
spotify-player:533
```
For whatever reason the same iframed app works fine with Safari and Firefox; but does not with other Chromium browsers like Opera for instance...
Update: looks like Chrome Canary works on Android. Not ideal but works for me.
Any update from anyone on this? Hasn't been working for me either, not even on the current Canary version of the app. Also, is anyone experiencing degraded performance on the Web Player?
I'm just here to upvote this and stay looped in on this issue if it ever gets fixed for Chrome. It's really annoying to have to use other browsers for my SDK player to work
Hi all
I solved it by resetting the "Protected Content" setting in chrome to "Always Ask" this then reprompted me to permit play protected (DRM Content) on my website when I next reloaded it. After that I found the Spotify player worked perfectly. It maybe that once you do this you can put the setting back to "Always allow" but on my machine(s) (idPad, Android, Desktop) it seemed to reset a setting somewhere.
Hope this helps!
Guidcruncher
For info I found out info on how to enable/reset DRM here https://www.devicemag.com/enable-drm-chrome/
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…