Buf fix (ESN parsing): Update xmldialog_esnwidevine.py
Thanks for the add-on. This is my first bug fix pull request, after founding a couple of lines to be changed when investigating current add-on problems (no video playback after 2 mins).
Description:
-
Please, note that valid Web browser ESN have only 2 '-' (the same format generated when resetting settings).
-
Also, additional Android patterns are used today (as you can check decompiling APK from https://github.com/aidanmacgregor/Netflix_ATV_L3_DRM_Uncertified_Mod).
Final Note: This changes will allow users to test additional ESNs on different platforms to see if it affects the playback issue.
Regards!
This changes will allow users to test
it is not a task of users to randomly make attempts without known what they are doing
would have made sense if this PR provide a working use case or at least proven that new ESNs are shown and used on the original apps usually different types of ESNs have a specific purpose, and you provide no details nor theory basis
Also, additional Android patterns are used today (as you can check decompiling APK from https://github.com/aidanmacgregor/Netflix_ATV_L3_DRM_Uncertified_Mod).
you base your findings on unofficial code, not a good way to investigate, must be taken official android release and decompile it also must to consider that the TV and mobile android versions are different, and must be compared both
the fix on "count" not tested but should be ok anyway i will not merge this PR as is
Good afternoon,
You have the right to merge or not this PR, but I would like to clarify my points in case you reconsider your position. Upon reviewing my previous message, it's clear that I did not express myself correctly or in detail the first time.
This changes will allow users to test ==> This change will allow users to manually write known and valid ESNs
ESNs differ from browser to browser, and it is documented that browsers limit available resolutions for streaming (source: https://help.netflix.com/en/node/23931).
ESNs can be retrieved from the browser using devtools (this includes the Windows app, which is essentially an encapsulated browser). I believe this could be a valid use case.
Regarding Android ESNs, I have checked all my certified devices, and they still use the coded pattern (NFANDROID1-), so I cannot prove that the official app is using a new pattern. However, I use the referenced unofficial APK on an uncertified device (XGIMI projector), and that’s the only way Netflix works on it. I thought this might be sufficient proof to accept the new pattern.
That said, I want to express my admiration for your efforts with this plugin, and I look forward to future releases.
Have a great day.
closed since i decompiled original apps and i havent found these new prefixes