|
ADC Bug Reporter FAQ
What do I do if I experience issues connecting
to the Bug Reporter?
If you are experiencing issues when connecting to
the Bug Reporter or if you have forgotten your password, please let us
know by completing this form. If you would
like to submit your bug report without using the Bug Reporter please use
the Bug Report Form.
Where can I get assistance with writing a bug
report?
For assistance with writing a bug report, please
see the Apple Bug Reporting Guide.
How do I check the status of bugs that were submitted
via email or by using the Bug Report Form?
Please send requests to devbugs@apple.com
and make sure to reference the Bug ID Number.
How do I add additional information to a bug
that I have already submitted?
Updates can be made to a bug that you previously
reported via the Bug Reporter by logging into the Bug Reporter, going
to “My Originated Problems”, clicking on the appropriate Bug
ID Number and adding your additional information where it says “Append
Problem Description Here”. Once you have saved the form the updated
information will appear in your bug report.
Updates can also be sent via email to devbugs@apple.com.
Please remember to reference the Bug ID Number of the original bug report
and we will make sure that the additional information gets attached to
the appropriate bug report.
How do I send Crash Logs and Apple System Profiler
Reports that are too large for the Bug Reporter?
After filing your report using the Bug Reporter you
will receive a Bug ID Number. Please send crash logs and ASP reports to
devbugs@apple.com. Please remember
to reference the relevant Bug ID Number. We will make sure that the additional
information gets attached to the appropriate bug report. You may
also click on the “Email Enclosure to Apple Developer Connection”
link after you have submitted your report and submit your attachment directly.
Crash logs are very useful in helping our engineers debug crashing bug
reports. To obtain a crash log, launch Console to turn on the crash reporter.
Then go to Preferences and mark the checkboxes under the Crash tab. After
you reproduce the crash, a window will appear containing the crash log.
When a kernel panic occurs, our engineers require a backtrace in order
to further diagnose the issue. In Jaguar, backtraces are saved to nvram
on restart/shutdown, then copied to the panic.log file on restart. You
can find this file in ~/Library/Logs. If you are not yet on Jaguar, you
must reproduce the panic and manually copy down all of the numbers that
are displayed on your screen when the panic occurs.
How do I request a workaround
for a bug report?
Workarounds are considered to be Technical Support
incidents. You must purchase Technical
Support if you would like to receive a workaround. Apple's Worldwide
Developer Technical Support Engineers will review your issue and assist
with a workaround if one is available. Unfortunately, we can not guarantee
that a workaround is possible for any given bug report. Please
note: WWDTS does not provide up-and-running
technical support. For a complete listing of support options for up-and-running
user-level assistance with Apple software or Apple hardware, please refer
to the following web sites:
http://www.apple.com/support/
http://www.apple.com/support/products/overview.html
Where do I send my feedback about the Bug Reporter?
Please use the Bug Reporter to report bugs or enhancement
requests on the Bug Reporter. If you have any issues, questions, or comments
about the Bug Reporter, please send feedback to
ADC Programs.
If I am still seeing an issue for a bug that
was closed, how do I reopen the bug?
If you are still encountering an issue that you have
filed via the Bug Reporter and the status for that report indicates that
it has been closed, please send an email to devbugs@apple.com.
The issue will then be reopened and reevaluated with our engineering team.
Important: Please remember to reference the
relevant Bug ID Number.
Are there any other ways to submit bug reports
to Apple?
Yes, Apple offers the following options:
- Apple Software Customer Seeding
Apple Software Customer Seeding is a program wherein customers are invited to test pre-release software products in order to provide Apple Software Engineering with real-world quality and usability feedback.
This program gives you a first look at new and upcoming software products while empowering you with the ability to provide feedback directly into engineering.
Software seeding is not for everyone. Participants testing developmental software must tolerate the unpolished nature of a pre-release product. There is always the risk of data loss.
- Apple Discussions
If you have a question about a technical issue you experience with an Apple product, or feedback of a technical nature you want to give to Apple, this is the place to do it. Your post will be available to customers with Internet access worldwide. If you can answer a question or offer a suggestion that may assist another user on the forum, we welcome and encourage your participation.
This area is intended to address technical issues. Discussions of Apple policies and procedures, speculation on Apple decisions, questions about products that have not been released, and issues with repair procedures are not appropriate. Discussion posts that are not directly related to a technical support issue, are only complaints, or contain abusive language are not appropriate. Posts that are not appropriate will be removed from the discussion forum.
| 
