different assetid in SPC coming from iOS client and Safari client

Question

Created Oct ’15

Replies 2

Boosts 0

Views 1k

Participants 3

Hi,

We are parsing the assetID from the SPC payload to identify the content on the server. However, we are getting different results for SPCs coming from iOS and from Safari.

We use the included reference clients for testing. Here's how we set the initData/create the requests:

iOS:

requestBytes = [loadingRequest streamingContentKeyRequestDataForApp:certificate
                                                      contentIdentifier:assetId
                                                                options:nil
                                                                  error:&error];

Safari:

initData = concatInitDataIdAndCertificate(initData, contentId, certificate);

where concatInitDataIdAndCertificate is exactly as provided in the sample code.

In both cases, we use the sample streams with content/assetId "twelve".

For the SPC from iOS, we get the correct asset ID:

7477656c7665

which translates to

twelve

If the request comes from Safari, we are seeing this:

e79db4e6b1a5e695b6000000

Can you please advise?

is this also the reason why the Safari example includes the assetId as additional URL parameter which is not the case on iOS?

Thanks and best regards,

Tobias

Boost

Answer 1

DTS Engineer OP

Apple

Oct ’15

There was an error in the example javascript code (FPS_in_Safari_Example.html) provided in the SDK package. This has now been fixed, and an updated SDK has just been posted to the web site (<https://developer.apple.com/streaming/fps/>). Please download the new SDK package and try this again.

0

Answer 2

solidwrist OP

Mar ’17

I am having a similar issue with the ContentId if the license request made by a Safari client. When the ContentId bytes are extracted from the SPC and converted into string, a corrupted string like unicode chars in it comes up.

But when the license request is made by an IOS client I can parse the ContentId without a problem with the same server side code.

What might be the issue here?

Can you please help?

Thanks,

Barbaros.

0