getting widevine-license error on the spotify web player
See original GitHub issueI started building a Spotify electron app a while back using the casklabs electron build, it worked fine back then (nearly a year ago). However spinning up the app now U see an issues where Spotify playback starts, then skips tracks then stops.
Looking in the console I am seeing requests being made to https://api.spotify.com/v1/widevine-license/v1/audio/license?exp=1587806765&cp=&tok=xxxxx
These fail with a 500 error message saying widevine error
. I am not making these requests so am wondering if electron is making these by default?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:30
Top Results From Across the Web
[web player] Always fail playing first 5 songs ("5... - Page 2
The 5th song starts to play successfully but stops after 10 seconds. I can reproduce this problem 100% of the time, regardless of...
Read more >Spotify Web-Player broken | Vivaldi Forum
Hey everybody, since two weeks I cant use the spotify web-player in my vivaldi browser. When i start a song, the player automatically...
Read more >Did Spotify Web Player stop working for you? : r/surfaceprox
I updated Microsoft Edge to the latest version, and Spotify Web Player refused to work because of DRM. Widevine Integration Platform.
Read more >Spotify requires I enable DRM & gave instructions how but ...
I tried to open the spotify web player. It said "Playback of protected content is not enabled." It gave me instructions, saying "Enter...
Read more >Spotify web player is not working any more - Brave Community
Spotify no longer supports this version of Chrome. Please update your browser for uninterrupted listening. ... These errors are not there in ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@khwaaj Victory! Changing the signing order fixed all the assets for me! Thank you so much!
To recap, the solution that worked for me was to: Sign Electron First:
python ./node_modules/electron/vmp-resign.py -C ./VMP/Signed\ by\ widevine/prod-movideon.der -P "MyPassword" -K ./VMP/production-key.pem -v ./node_modules/electron/dist
Build the app and sign with CodeSign using electron-builder:
sudo npm run prod
Verify the signature afterwards:
python ./node_modules/electron/vmp-resign.py -vv -Y -M "MyPlayer.app" -v ./build/mac/
This behavior is actually documented in the link I provided above and it relates to how code-signing and VMP-signing works and interacts on the different platforms.
On Windows, like in this case, the code-signing makes changes to the executable itself to store the signature that is generated. The VMP implementation on Windows does not allow any changes to a signed executable, so if the VMP-signature is generated before code-signing it will be broken by the change that code-signing makes. On macOS it is the opposite because of how app-bundles, code-signing and VMP-signing interacts there.