New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 772120 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocked on:
issue 700147



Sign in to add a comment

Not prompted to allow for unique identification when attempting to play WideVine DRM content

Reported by michael....@gmail.com, Oct 5 2017

Issue description

Example URL:
https://shaka-player-demo.appspot.com/demo/

Steps to reproduce the problem:
1. Go to URL
2. The page does not completely load.

What is the expected behavior?
I should be prompted to uniquely identify my device to view DRM protected content.

What went wrong?
Can't play DRM content!

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 7.1.1
Flash Version: 

Contents of chrome://gpu: 
Unable to copy this from Android phone easily.

This doesn't happen on all phones... I am using a Samsung Galaxy S6. Resetting credentials also does not work.

More information and screenshots can be found @ https://github.com/google/shaka-player/issues/952
 
Cc: xhw...@chromium.org ericde@chromium.org
Have you ever blocked the prompt on this test page? To check it out, go to Settings -> Site settings -> Media -> Protected content, and check
1. Whether "Protected content" is enabled or not.
2. Whether there's any site in the "Blocked" list.
Thank you for the rapid response. Under protected content, I am seeing 'Ask first'. I do not see a Blocked list.
Cc: joeyparrish@chromium.org
From what we saw on Shaka Player's github issue [1], it would seem that requestMediaKeySystemAccess() succeeded, but createMediaKeys() failed with "DOMException: Unsupported keySystem".

Nobody on my team was able to reproduce, but that is what appears to happen according to the information and screenshots provided.

I am not aware of any circumstance that would cause requestMediaKeySystemAccess() to succeed and then fail at createMediaKeys(), but hopefully this is a useful clue to the code path that would lead to this in Chrome.

Please let me know if I can do anything to help.

[1]: https://github.com/google/shaka-player/issues/952

Comment 6 by xhw...@chromium.org, Oct 10 2017

Blockedon: 700147
I am planning to add UMA for createMediaKeys() result, and hopefully that'll give us stats on how often this call fails. This is tracked by  issue 700147 .
Thank you much for the support on this! The only thing I can think of and as I am not a DRM expert I wanted to ask...

Could it be that my device screen was replaced after being cracked?

I also read something about resetting the phone cache while in the bootloader, which I have tried on other devices but not my personal.
Cc: -xhw...@chromium.org
Owner: xhw...@chromium.org
Status: Assigned (was: Unconfirmed)
since 700147 is fixed. UMA for createMediaKeys() is retrievable.
give to xhwang@ to follow up with reporter on how to get UMA data.
Status: WontFix (was: Assigned)
I checked the UMA and indeed there are cases where createMediaKeys() fails on Android, which is not surprising because the number of concurrent MediaDrm instances is limited due to hardware limitations.

Given that we cannot repro, and this only happens on one device, I intend to mark this as WontFix.

If you have other steps that we can follow to repro please feel free to reopen.
Thanks, guys! I appreciate the investigation.

The only thing I can think of is does DRM or ability to use DRM become invalid after you replace your screen on your phone? Like are there any SN's written or logged that if change invalidates your ability to watch DRM content?

I will keep this in my bookmarks and if I see it again or on other devices I will bring to your attention again!
Thanks for the update! I don't know about Android enough to answer your question unfortunately.
Actually I checked. Replacing the screen should NOT affect MediaDrm. But again I have no idea what's wrong with that particular device.
Thank you! This can be closed for now I will also close the relating bug in Shaka will re-open if we can find a device model or steps that can be reproducible on more than just one or two device models.

Sign in to add a comment