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

Error setting a custom asset with certificate. #1914

Closed
avelad opened this issue May 6, 2019 · 2 comments
Closed

Error setting a custom asset with certificate. #1914

avelad opened this issue May 6, 2019 · 2 comments
Assignees
Labels
component: demo page The issue is in the demo page; does not affect production applications status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Milestone

Comments

@avelad
Copy link
Collaborator

avelad commented May 6, 2019

Have you read the FAQ and checked for duplicate open issues? Yes

What version of Shaka Player are you using? Master

Can you reproduce the issue with our latest release version? N/A

Can you reproduce the issue with the latest code from master? Yes

Are you using the demo app or your own custom app? Demo App

If custom app, can you reproduce the issue using our demo app?

What browser and OS are you using?
Safari 12.1 Mojave

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

Any with a certificate url (with a fake custom asset the issue is reproducible)

What did you do?

Create a custom asset with certificate uri

What did you expect to happen?
No errors

What actually happened?

Uncaught (in promise) TypeError: Cannot set property 'serverCertificate' of undefined
at ShakaDemoMain.drmConfiguration_ (main.js:693)
at async ShakaDemoMain.loadAsset (main.js:725)

I think that the issue is in https://github.com/google/shaka-player/blob/master/demo/main.js#L693

@theodab theodab added type: bug Something isn't working correctly component: demo page The issue is in the demo page; does not affect production applications and removed needs triage labels May 6, 2019
@theodab
Copy link
Collaborator

theodab commented May 6, 2019

Thanks for the report! License server certificate URI is, admittedly, a feature I haven't tested very much, so it's likely I introduced some bug into it during a refactor or something. I'll look into it.

@shaka-bot shaka-bot added this to the v2.5 milestone May 6, 2019
shaka-bot pushed a commit that referenced this issue May 8, 2019
Issue #1914

Change-Id: Ia5260280c5f1dd8bd596cb6bf5b3f47126fc3038
@theodab
Copy link
Collaborator

theodab commented May 8, 2019

I fixed the bug you found.
I'm not entirely sure whether or not the actual certificate URI field works as intended; every bit of sample content I've found to test it has had some kind of unrelated issue or another (CORS errors, missing resources, etc).
So I'm going to close this issue. If you have some private content of your own which can verify whether or not the field works, we'd be happy to fix any bugs you find.
Thanks for the bug reports!

@theodab theodab closed this as completed May 8, 2019
shaka-bot pushed a commit that referenced this issue May 8, 2019
If the demo fails to fetch a cert for custom content, it will now
catch and display the error.

Issue #1914

Change-Id: Ib058cdcf8d90b675b3624c264ec7a80909d1cc47
joeyparrish added a commit that referenced this issue May 20, 2019
If the demo fails to fetch a cert for custom content, it will now
catch and display the error.

Issue #1914

Change-Id: Ib058cdcf8d90b675b3624c264ec7a80909d1cc47
@shaka-project shaka-project locked and limited conversation to collaborators Jul 7, 2019
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
component: demo page The issue is in the demo page; does not affect production applications status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Projects
None yet
Development

No branches or pull requests

3 participants