Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netflix ERROR M7121-1331 #122

Open
jiameng15 opened this issue Feb 22, 2022 · 7 comments
Open

Netflix ERROR M7121-1331 #122

jiameng15 opened this issue Feb 22, 2022 · 7 comments

Comments

@jiameng15
Copy link

jiameng15 commented Feb 22, 2022

Thanks for releases electron 17.0.1+wvcus.
When I use this releases to solve the problem of origin Electron without Widevine CDM component,it works.
But there a new problem , Netflix show me the new error , error code is M7121-1331.
How can i solve this problem, or can't be solved, look forward to your reply and thank you.

Demo address: DEMO

@khwaaj
Copy link
Collaborator

khwaaj commented Feb 22, 2022

While I'm not privy to the meaning of the error codes used by Netflix I'm pretty sure this has to do with the Widevine VMP requirement. Did you read the How does it work section of the README?

The published releases are only VMP pre-signed for development and will not work with commercial services, like Netflix. To instead generate a production VMP signature you can register for our VMP signing service, EVS, which allows you to generate a production VMP signature for your application. The linked Wiki page above documents how to register and use EVS.

@coreybruce
Copy link

@jiameng15 If you want a working Netflix desktop app for app platforms, I have made one which now supports Windows

https://gitlab.com/netflix-desktop/binaries/1.0.5-1

@V0l-D
Copy link

V0l-D commented Nov 7, 2022

While I'm not privy to the meaning of the error codes used by Netflix I'm pretty sure this has to do with the Widevine VMP requirement. Did you read the How does it work section of the README?

The published releases are only VMP pre-signed for development and will not work with commercial services, like Netflix. To instead generate a production VMP signature you can register for our VMP signing service, EVS, which allows you to generate a production VMP signature for your application. The linked Wiki page above documents how to register and use EVS.

Will we ever see commercial support for it? or new versions for the wvvmp version.

@khwaaj
Copy link
Collaborator

khwaaj commented Nov 7, 2022

Will we ever see commercial support for it? or new versions for the wvvmp version.

Not sure I follow, both the old wvvmp and the new wvcus versions of ECS support commercial services as long as you VMP sign yourself, i.e. using our free EVS service. EVS generates production signatures, which will make your app work with commercial services, it is just the published releases that are pre-signed for development only (and always have been).

@V0l-D
Copy link

V0l-D commented Nov 8, 2022

How am I still getting the M7701-1003 error code then when I sign it using EVS, I've signed before on wvmp versions which works fine but it somehow does not work when I do it on wvcus could you explain why it still fails?

@khwaaj
Copy link
Collaborator

khwaaj commented Nov 8, 2022

Well, I don't know what version you are using, what platform you are on, or exactly how you are signing, so it is a bit hard to help out.

I just confirmed however that v22.0.0-beta.3+wvcus on macOS gives the original M7121-1331 error on Netflix when using a development signature (or no signature at all). After I sign with EVS playback works fine, without any errors. There are multiple things that can break your signature, or make you sign the wrong ECS instance (e.g. when using something like electron-builder vs just running npm run start), so make sure you are following the available instructions (and search the issue archives, many things have been discussed there over the years).

I'm not exactly sure what the Netflix error M7701-1003 means, but it seems related to the CDM not being available/loaded. Two potential things that come to mind are:

@V0l-D
Copy link

V0l-D commented Nov 9, 2022

Okay figured out the issue components.whenReady() was not properly configured, thanks for the help I appreciate it a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants