Core Media errors should be better described and documented

Errors related to media playback, whether received from AVPlayer directly or read from an AVPlayerItem access log, usually lack information about the root cause of a playback issue.

Most errors we receive in the CoreMediaErrorDomain are namely associated with undocumented error codes and non-explicit error messages.

Here are a few examples:

  • Error Domain=CoreMediaErrorDomain Code=-12927 "(null)"
  • Error Domain=CoreMediaErrorDomain Code=-16012 "(null)"
  • Error Domain=CoreMediaErrorDomain Code=-12685 "The operation couldn’t be completed."
  • Error Domain=CoreMediaErrorDomain Code=-12648 "The operation couldn’t be completed."

It would be helpful that Core Media:

  • Provides a public constant for the CoreMediaErrorDomain.
  • Provides public constants for the error codes within this domain.
  • Ensures each error is associated with a meaningful human-readable description.

If not possible having at least a documented list of error codes (as is done in the FairPlay programming guide PDF, for example) would allow us to better classify errors and understand playback errors experienced by our users.

I opened a FB17673165 feedback with this suggestion as well.

Thanks in advance for considering this improvement request.

@defagos It seems like you open this bug long time ago and the team has been communicating with you using the Feedback Assistant?

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Hope this helps

Albert  WWDR

Thanks for your answer.

You are right, I opened this issue more than a year ago, but since I never got any feedback in Feedback Assistant and the issue status was never updated I assumed discussing it here could help move things forward a bit.

@defagos Thanks for providing that feedback, I'll add a note on the bug.

Thanks again for your quick reply.

Albert  WWDR

Core Media errors should be better described and documented
 
 
Q