How do I submit a bug or an enhancement request?

The Apple Bug Reporter can be used by all registered Apple Developers to submit their reports. Log in to the Apple Bug Reporter to file and submit a bug report or enhancement request.

Where can I find information about writing a complete bug report?

Bug Reporting Best Practices outlines steps to writing a thorough, actionable bug report.

Which browsers are supported by the Apple Bug Reporter?

The Apple Bug Reporter supports the following browsers:

Can a report be filed from iPhone?

Bug Reports can be submitted from your iPhone or iPod touch. File uploads are not supported. Files will need to be uploaded from your host system. Information on obtaining crash logs can be found below or from Bug Reporting Best Practices.

How do I report problems accessing the Apple Bug Reporter?

The Connection Problems Form can be used to report the issue.

Note: Cookies and JavaScript must be enabled on your browser for the Apple Bug Reporter to function properly. While the issue is being investigated, reports may be submitted using the Bug Report Form.

Where do I send my feedback about the Apple Bug Reporter?

Any bugs or enhancement requests regarding the Apple Bug Reporter itself can be submitted as a report within the tool.

Where can I find more information on what features the Apple Bug Reporter has to offer?

The 'Help' tab provides site definitions, searching guidelines, timeout information, and links to other Bug Reporter resources.

What happens to a bug report after it is submitted?

Upon submission of a bug report via the Apple Bug Reporter, the report is stored in our bug database and reviewed by Apple engineers. We will contact you if additional information is required to investigate the report, as well as to provide the resolution of the issue.

Will I receive any communication regarding my bug report?

We will contact you if additional information is required to investigate your report, as well as to provide the resolution of an issue you reported. To request a status on your report, update your bug report directly with your request and someone will respond to you with a status update.

How do I add information to my bug report?

Information, including files, can be added from the 'My Originated Problems' tab by clicking on the Bug ID# that you wish to update.

Are there times when more information is necessary to process a bug report?

In addition to the basic information required for a bug submission (Summary, Steps to Reproduce, Expected Results vs. Actual Results, Workaround, System Regression & Configuration Information), the following types of issues need specific information in order for engineering to investigate the report:

Kernel Panic:

panic.log file from /Library/Logs. If you are unable to find the correct panic.log file, the most recent panic information may still be in nvram. Try entering "nvram -p" on the command line to retrieve the file.

Crash:

crash.log from ~/Library/Logs and a reproducible case if related to Xcode, Java or Safari.

For a crash related to Mail.app, also include the raw source of the message in question, which can be retrieved by following these steps:

1. Open the message you want to export.
2. Choose File > Save As, and enter a name for the file.
3. Choose a location for the file from the Where pop-up menu.
4. Choose a Raw Message Source format from the pop-up menu.

For crashing issues on iPhone, sync your iPhone with iTunes and check the following location on your host machine:

• For Mac Users: /Library/Logs/CrashReporter/MobileDevice/
• For Windows Users: Application Data/Apple Computer/Logs/CrashReporter/MobileDevice/

Hang or Freeze:

Sample of the application while hung:

This can be taken from the Activity Monitor or Terminal. More information about using "Sample" can be found by typing "man sample" in the Terminal.

When is a configuration file required?

A System Profiler report or Windows system file is required for crashing or kernel panic issues, as well as reports against hardware or printing.

As a Windows user, what configuration information should I submit with my report?

A text file must be uploaded containing the Windows system, as well as Apple Software version and build numbers.

How many files can be uploaded to a bug report via the Apple Bug Reporter?

There is no file limit per bug report, although only one file per 'Choose File' location can be uploaded at a time.

Specifically, when submitting a new bug report, two files may be uploaded - Configuration Section & Additional Enclosures Section. Additional files can be added at anytime to a bug report from the bug submission confirmation page, or from the 'My Originated Problems' page clicking on the Bug ID number.

Is there a file size limitation for enclosures when using the Apple Bug Reporter?

Each file must be under 50MB. If the file is slightly over the limit, try compressing it. If the file still exceeds the size limitation, update your bug report with comments indicating that you need assistance providing a file larger than 50MB and we will contact you with instructions on how to access our FTP site to upload your file.

Is it possible to upload folders to a bug report?

Folders can be uploaded within the Apple Bug Reporter if compressed as a file.

What should I do if I experience problems uploading files to the Apple Bug Reporter?

Contact Bug Reporting, making sure to include your Bug ID#, file(s), browser version, screenshot, and description of the upload issue.

I am receiving an error when uploading a file to my report. What can I do?

There are some files that include a bundling of applications or files. If you receive an error message while trying to upload a file (like an NSPOSIXError Domain error) try compressing the file and uploading the file again. If you still experience issues attaching the file, email Bug Reporting with your file and we will attach it to your bug report and investigate the issue.

How can I retrieve a file that I previously uploaded to my bug report?

Files that you previously attached to a bug report can be accessed and downloaded to your desktop. From the 'My Originated Problems' page click on the Bug ID number and the File Enclosure icon will display your files. If you are unable to view or download your files, email Bug Reporting.

Why do some of my reports appear in red text in 'My Originated Problems'?

Red text indicates that the bug report requires your attention. Engineering either needs more information to investigate the reported issue, or has information to relay to you. Once you have updated the bug report, engineering will be alerted to the new information and the bug will no longer appear in red.

What do each of the different tabs mean that are displayed under 'My Originated Problems'?

Bug reports are separated into the following categories:

• Attention: Issues requiring your attention are now grouped together in one section
• Open: Issues listed here are currently open and still being investigated
• Closed: Issues listed here include any bug reports that you have filed and that have been closed
• Archived: Issues listed here are older issues that have been closed.

Note: Issues that have been closed with a final resolution of Insufficient Information, Behaves Correctly, Duplicate, and 3rd Party to Resolve will be reflected accordingly.

How do I filter my list of bug reports under the 'My Originated Problems' tab?

Filtering your problem list can be done by 'Product', 'Classification', and 'State'. Select the item in the drop-down list that you wish to filter by and filtering is automatically initiated. You can also apply multiple filters simultaneously, for more granular filtering.

How do I change the number of bug reports that I can view on a single page?

You may select the number of results per page in increments of 25 up to 100, or opt to show all your problems within a category by selecting '>100'.

What are the different ways that I can search for my bug reports?

You can search for your submitted bug reports by individual Problem ID, Title, Originated Date, Notes, Problem Description, or by any combination of the above. Wildcards ("%" and "_") are available for text searches within any of the searchable fields, and the Originated Date can be searched using greater than, less than, and a date range. Search results can be further refined by filtering and sorting by columns to find exactly what you're looking for. More details can be found under the 'Help' tab of the Bug Reporter.

How do I search by a single word that will pull up any bugs that have that word in the report?

It is possible to do a single word or string text search within the Title, Notes, or Problem Description fields by using the '%' as a wildcard. More details can be found under the 'Help' tab of the Bug Reporter.

How can I check the status of my submitted bug reports?

Status of your bug report is accessible via the 'My Originated Problems' tab of the Apple Bug Reporter under the 'State (Definition)' column.

If you need additional information or want to request a status, you may contact Bug Reporting and reference your Bug ID number and someone will respond to you with a status update.

My bug report has been flagged as Behaves Correctly/Duplicate/3rd Party to Resolve in the Apple Bug Reporter. How can I get more information on how Apple came to that conclusion?

While the 'State' of the report will reflect this resolution in the 'My Originated Problems' tab, further elaboration is often visible in the 'Notes' section of the problem detail view of the report. If you have further questions, update your report with your comments and they will be reviewed.

How can I track the status of an original bug report when my bug has been closed as a duplicate?

Bugs closed as a duplicate will show 'Duplicate' in the 'State' column of your problem list. Additionally, the original bug number under which the issue is being tracked will be provided. It will look like this:

State: Duplicate/1111111

To request a status update for your reported issue send an email to Bug Reporting.

Can I close my own bug report?

You can flag a report to be closed by clicking on the 'Resolved' checkbox on the 'My Originated Problems' detail page for the bug report.

How do I reopen a closed bug?

If you are still encountering your reported issue, but the status is closed, update your bug report directly to that effect and Engineering will be notified to reopen the bug report.

Can a workaround for a bug report be requested?

Workaround requests are considered Technical Support Incidents. You must purchase a Technical Support Incident if you would like to receive a workaround. Developer Technical Support Engineers (DTS) will review your issue and assist with a workaround if one is available. We cannot guarantee that there will be an available workaround. DTS provides code-level support. For up-and-running support, please contact AppleCare at 1-800-MY-APPLE.