Bug Reporting

Apple greatly appreciates the efforts of developers who help to discover and isolate bugs within our products.

Note: Please do not use this form to submit a request for a workaround. Workaround requests must be submitted to our Developer Technical Support (DTS) Team. You must already have or purchase a Technical Support Incident in order for DTS to investigate a workaround. However, neither we nor DTS can guarantee that a workaround will be found for the issue you are experiencing.

If you would like to find out if there is a solution to the problem you are experiencing without purchasing a Technical Support Incident, please explore the Apple Customer Support options.

For information about joining Apple Developer Programs, please visit Apple Developer Programs.

To learn more about how to submit a good bug report, review our Bug Reporting Best Practices.

All of the following fields are required to process this report. Enter 'N/A' in fields that are not applicable.

Restate the problem title and/or include more descriptive summary information.

Include any setup or preparation work and the steps we can take to reproduce the problem.

Describe your results and how they differed from what you expected.

Is there a workaround?

Document any additional information that might be useful in resolving the problem.

Crashlogs are very useful in helping our engineers investigate Mac OS X bugs. To locate a crash log, please check one of the following locations:

  • ~/Library/Logs/CrashReporter
  • /Library/Logs/CrashReporter

When a kernel panic occurs, our engineers require a backtrace in order to further diagnose the issue. Backtraces are saved to nvram on restart/shutdown, then copied to the Kernel_<date and time>_<machine name>.panic file on restart. You can find this file in /Library/Logs/DiagnosticReports

To ensure our engineers can successfully test bugs, full System Profiler reports should always be included with bug submissions. Please submit your full System Profiler report via the System Profiler application, which generates an .spx file. Then, send this file to the Developer Bug Reporting Team.