Have you received any feedback from Apple or even found out what was the problem? It may not be related but I'm currently having a CoreMediaErrorDomain -12035 error using the same AV adapter when streaming FairPlay-protected content but only on iOS 18+. It works fine on iOS 17.7. https://developer.apple.com/forums/thread/770159

Thanks for your response. I filed a bug report on Feedback Assistant with the following id: FB16047318 (CoreMediaErrorDomain -12035 error when playing a Fairplay-protected HLS stream on iOS 18+ through the Apple lightning AV Adapter).

Sure: https://feedbackassistant.apple.com/feedback/16902752

Actually the problem is even worse: the AVPlayer.currentTime() does not change anymore after the playback transitions from AirPlay (to an Apple TV) to local despite the playback still ongoing. Also, it's worth noting that when the issue occurs, AVPlayer.currentDate() is properly updated. So the problem is probably not related to the periodic time observation but rather to the AVPlayer.currentTime() not being updated anymore when switching from AirPlay to local playback.

I have reported the issue with Feedback assistant: https://feedbackassistant.apple.com/feedback/17172515 I have also included a sample project allowing to easily reproduce the issue.

Some of our end-users experience the same issue with offline content keys. We had to disable content key persistence support until we fix the issue. I even reproduced it once myself with a valid (ie. not expired) offline content key: once providing the offline content key to the AVKeyRequest, the system immediately fails the AVPlayerItem (no automatic retry at AVContentKeySession level) with error CoreMediaErrorDomain:-42650. It is systematic and can only be solved by deleting the offline content key from the app content key store (which forces the app to retrieve a new content key from the KSM). Unfortunately, offline content keys lease duration being 30 days, it is not easy to reproduce the issue and provide logs. Could Apple provide more information on this error specifically and on CoreMediaErrorDomain errors in general? The lack of documentation is very annoying and developers can only empirically list errors when they occur (examples: https://developerinsider.co/fairplay-streaming-error-codes/, https://developer.bitmovin.com/playback/docs/system-error-codes-ios).

Thanks Quinn for your answer. Everything makes sense now and we are relieved that you confirmed that the arguments evaluation is done in the logging call thread.