-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Tizen 2017 misreports support for persistent licenses #894
Comments
Tizen 3.0 web app user agent string, for reference:
|
In the original failing test ("Offline stores, plays, and deletes protected content"), the platform doesn't fail the persistent license flow until the license response is given to the CDM. We now have an additional failing test (new test added in #878):
With logging turned on, the new failure shows the error "Must not be destroyed", which is ambiguous. |
The new test is failing because |
This works around Tizen 3.0's misreporting of its support for persistent licenses, which prevents us from running persistent license tests on that platform. There is still one more failing test on this platform. Issue #894 Change-Id: I81ebb80a831c753e3af4851efcbd7e97211e6890
Discovered while working on #894 Change-Id: Icf74cd4bf804df0b055033f9c1113971e1644202
Work-arounds are in place now, but we still have not been able to file bugs against Samsung/Tizen. Having trouble getting an account on their JIRA instance. |
This works around Tizen 3.0's misreporting of its support for persistent licenses, which prevents us from running persistent license tests on that platform. There is still one more failing test on this platform. Issue #894 Change-Id: I81ebb80a831c753e3af4851efcbd7e97211e6890
Discovered while working on #894 Change-Id: Icf74cd4bf804df0b055033f9c1113971e1644202
Work-arounds have been cherry-picked and will be released in v2.1.5. |
Samsung will never fix this, so there's no need for us to continue tracking it. I'm closing it now. |
It would appear that Tizen TVs claim support for persistent licenses, but do not actually support them. We should:
DrmEngine.probeSupport
The text was updated successfully, but these errors were encountered: