getting widevine-license error on the spotify web player

I 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?

[turbidwater]

@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/

[khwaaj]

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.