I have exactly same problem as palethorn's one. Safari EME does not generate any SPC message.
(We are using dev_certificate.der)
It is pleased if someone could give us a direction.
I'm assuming that safari 10 checks for certificate validity and doesn't generate SPC when it's not valid. I downgraded my testing machine to el capitan with stock safari 9 for preliminary testing just for the time being. I'll post here after I check my assumptions later.
The information that the Apple staff have provided elsewhere on this forum states that you need to use a 'Real' client certificate as supplied with a deployment package.
Hi, were you able to figure out the issue? I'm not able to generate an SPC either. Do we need to install real certs?
I have a similar issue,
after updating the session with CKC message I'm getting a webkitkeyerror with
MEDIA_KEYERR_DOMAIN. In my case systemCode is always 1212433232.
Did any of you experience such errors? I could use a hint as the systemCode tells nothing.
in case you encounter this error - the above exception is HDCP telling you that you can't play. I was testing using remote desktop connection to a Mac and this is what the example app told me and there was no video to be seen.
When I ran the player straight on the Mac, playback worked like a charm.
Looks like HDCP is enforced by default, even if no HDCP enforcement TLLV is present in CKC.
I am getting the same error. webkitkeyerror is getting invoked on playing test content. I am using production fairplay credentials. Neither webkitkeymessage nor webkitkeyadded is getting invoked. I am using the sample test content.
Safari version - 11.0.2
Mac OS - 10.13.2
The sample content plays back correctly, when presented with the right key in the right format to the player. Is the below in sample content
enough for the player to request for a key?
Any help is greatly appreciated.
I've resolved this error by deploying correct production certificate and key on the key server. The provided certificate inside the example is expired and thus invalid. It can only be used for testing purposes as described in the SDK documentation. The procedure for requesting production certificate is also described inside the documentation.
>The procedure for requesting production certificate is also described inside the documentation.
Сould you please refer to a particular page of the document? I can't find anything corresponding
FPS Deployment Credentials are still valid and continue to work after they expire, there is no reason to replace them after they expire and a FPS server should not check their expiration. What is in the FPS SDK are development credentials for use when developing and testing a FPS development server. Like the deployment credentials are still valid for deployment after they expire, the development credentials are still valid for development and testing after they expire. This is a common misunderstanding.
You are correct that the information about requesting the deployment package is also in the FPS programing guide.
I have the same problem as the topic starter.
Is it correct that this problem is not related to the expired certificate in the SDK, as you say?
I'm trying to implement the FPS ready video playback-plugin for one popular html5-based player. And I don't have any backend yet to test with.