Search code examples
iosswiftobjective-cios16fairplay

iOS 16 FairPlay Changes


Are there any changes in FairPlay logic? My app has FairPlay protected Videos and Audio, they work perfectly until iOS 15.7, but in iOS 16

makeStreamingContentKeyRequestData is throwing me following error :

Error Domain=CoreMediaErrorDomain Code=-19152 "(null)"
Error Domain=AVFoundationErrorDomain Code=-11800 "The operation could not be completed"
UserInfo={NSLocalizedFailureReason=An unknown error occurred (-19156), NSLocalizedDescription=The operation could not be completed, 
NSUnderlyingError=0x280deac10 {Error Domain=NSOSStatusErrorDomain Code=-19156 "(null)"}}

What could be the possible reason for this and solution?

Thanks in Advance


Solution

  • We are using AVContentKeySession for downloading, met with the same error, and fixed it. For our case, the issue was as following.

    Issue observed:

    1. On iOS16.0.3, 12s later after "license request" was triggered firstly by app during downloading, "license request" would be triggered again by AVFoundation framework ("contentKeySession(_ session: AVContentKeySession, didProvide keyRequest: AVContentKeyRequest)" was called again), and then error “-19152“ wad reported quickly by framework. Error log: contentKeySession(_:contentKeyRequest:didFailWithError:), line: XXX, message: XXX, url: XXX, error is Domain=CoreMediaErrorDomain Code=-19152 "(null)"
    2. On iOS15.6.1, after "license request" was triggered by app during downloading, framework would not trigger any "license request" again.

    Root cause: iOS Framework API(AVContentKeySession & AVPersistableContentKeyRequest) behaviors changed on iOS16.

    Solution: Add “keyRequest.processContentKeyResponse(keyResponse)” after CKC has been downloaded on iOS16+.

    • On iOS11 - iOS15, we didn't call it after downloading, instead we only save persistentKeyData locally, and called processContentKeyResponse when playing. That always worked fine on these iOS versions.
    • But on iOS16 and above(until iOS16.1 Beta4 by now), the old process would trigger framework error. So we added this fix.