-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Offline Widevine DRM reporting (0,0) when calling getLicenseDurationRemainingSec on Android O #3112
Comments
@jefftinker - Sounds like offline DRM reporting might be broken in O on Nexus 6P. Any idea if this has been fixed, and/or if there are covering GTS tests? Thanks. |
Any progress? Problem still present on final release of Android O on Nexus 6p. The remaining LicenseDurationRemaining is always reported as zero seconds. Strange thing is that the DRM-protected content is playable despite of that. 0 = {HashMap$Node@8066} "PersistAllowed" -> "True" |
Looks like another user has determined a 'fix' work around for this. #3150 |
This is still a problem on Nexus 6p and Nexus 5x on final version of Android O. Changing rental-duration and playback-duration to small values like 84600 and 10000, does not help as the workaround suggests. |
@wvpaf - Can you please take another look at this? |
@janeriksamsonsen can you share content + license server URL so that we can investigate. If you need to share it privately and have a Widevine Technical Account Manager contact, share it with them and mention this issue. |
Will share links with you, but need to clarify with legal department first. We don't have a Widevine account manager. Can I send it to the email-address which I submitted the bug-report to? |
Yes, you can send it to that address. |
@rrfrias - our license server URLs are only valid for a certain amount of time. What would be a good day and time for you to test? |
URLs for content and license sent in email. Problem is also reproducible in DashWidevineOfflineTest.testWidevineOfflineExpiredLicense(). Reporting is correct for Xperia z1 compact with Android 6.0.1, but fails on Nexus 6p with Android O. |
Thanks for the URLs and for bringing this to our attention. The duration reporting issue has been fixed in O-MR1. The duration values set in the policy are uncommon and it might be worthwhile to revisit them and make sure they meet your needs. Usually offline licenses are controlled by rental and playback duration values. In your case rental is set to a limited value, while playback is set to unlimited. Querying could result in ambiguous results. For example "PlaybackDurationRemaining" -> "9223372036854775807" and "LicenseDurationRemaining" -> "0" may indicate either If you want more information about duration values and how to configure them please contact widevine-tams@google.com |
Thanks @rrfrias! |
@rrfrias, I've just tested with firmware OPP5.170921.005 for Nexus 6p, but the problem is still present. Is this the same as O-MR1? However, it seems to be working in the latest Android 8.1 emulator (OPM1.171004.001). |
Issue description
We're using the offline DRM functionality of ExoPlayer to allow offline playback of downloaded Dash-content in our app. This is working fine on all Android versions from 4.3 and up to 7.1.2. I updated my Nexus 6P to Android O beta (OPP4.170623.014), and the functionality for querying license-duration seems to be broken. Calling the function OfflineLicenseHelper.getLicenseDurationRemainingSec with a previously downloaded keyset-id always returns a pair with both values set to zero.
Reproduction steps
Download a Widevine DRM-license on Android O and call OfflineLicenseHelper.getLicenseDurationRemainingSec with the given keyset-id. Observe how the values in the returned value is always zero.
Link to test content
Please ask when ready to test, and I can provide a time-limited license-url.
Version of ExoPlayer being used
2.4.4
Device(s) and version(s) of Android being used
Reproduces every time on a Nexus 6p with Android O Beta (OPP4.170623.014)
Problems also present on Nexus 5x
A full bug report captured from the device
Sent in email.
The text was updated successfully, but these errors were encountered: