Offline FairPlay - possible on macCatalyst (Catalina)?

Question

karlg_arris OP

Created Sep ’19

Replies 7

Boosts 0

Views 2.0k

Participants 3

Hi,

We have an existing app and are experimenting with adding a target for macOS (Catalyst).

The only functionality that appears not to be working is offline playback (of FairPlay protected content).

We see that when we pass back a CKC that has either a time sensitive Content Key Duration TLLV or an Offline Key TLLV we get an error on calling:

[keyRequest persistableContentKeyFromKeyVendorResponse:...]

Like:

"Cannot Open" UserInfo={NSLocalizedDescription=Cannot Open, NSLocalizedFailureReason=This computer is not authorized to play (null).}

The error code is : -42668 (CKC invalid)

So the question is - Does UIKitForMac/Catalyst/Marzipan implementation of FairPlay support offline playback or not?

Boost

Answer 1

mathieu-fastpoint OP

Sep ’19

I think it's possible but I cannot accomplish offline playback too with Catalyst. Does Apple guys have a solution ?

0

Answer 2

mathieu-fastpoint OP

Oct ’19

I used a TSI to get help of Apple Support. They confirmed that macOS Catalina should support offline playback but this is a known bug. It'll be fixed on future versions (maybe 10.15.1 beta, otherwise, we should look for it in next release). Wait and see 😉

0

Answer 3

gabor.sajo OP

Oct ’19

I just tried with latest beta of MacOS Catalina 10.15.1 (19B86a) and still having the same issue with extracting the persistableContentKeyFromKeyVendorResponse

0

Answer 4

karlg_arris OP

Nov ’19

Still not working for me on :

macOS 10.15.1 (19B88)

0

Answer 5

gabor.sajo OP

Nov ’19

Also tried macOS Catalina 10.15.2 beta 1. Same error 😔

0

Answer 6

mathieu-fastpoint OP

Nov ’19

I sent a demo to Apple that confirmed that it fails on latest version. Before 10.15.1 release, they confirmed that this bug was resolved but I contacted them to indicates it's doesn't work yet.

I'm waiting for Apple response. They have to investigate on this bug from my demo project.

Apple response :

06/11/2019
Sorry about the delay in responding, but it looks like the fix for the problem we knew about was in 10.15.1, which means that you’re running into something else
[....]
Would you mind submitting a new bug report for 10.15.1, including a new sysdiagnose and steps to reproduce, and let me know the bug number?

08/13/2019 :
I’m able to reproduce the issue as you described, using your sample project. However, it’s going to be necessary for you to submit a new bug report, because the existing one has already been closed as a duplicate (because it looked like you were running into an issue that was fixed in 10.15.1)....

Waiting for response

0

Answer 7

karlg_arris OP

Feb ’20

This is resolved for me on:

10.15.4 Beta (19E234g)

Can you guys see the same thing?

0