Bug Reports: What Devs Need To Know
As always, for betas or releases, registered devs should feel free to use Report a Bug for any fixes, samples, doc additions, feature requests or enhancements you'd like to see as well. Provide detailed information for the issue, including the system and developer tools version information, and any relevant crash logs or console messages. Be prepared to submit a sample project that demonstrates the issue(s).
See: Report Bugs / Suggest Features to provide feedback directly to Apple.
• Each top level issue deserves a unique report.
• Posting in the Developer Forums is not reporting. Apple does not read those comments nor harvest information from them, so file bugs if you want to be heard. Add your report # to your thread for reference, thanks.
• When reporting an issue it is helpful to provide console logs, device* logs, and screenshots that illustrate the problem.
* iOS Devs should always collect and send along any/all related device logs when reporting a bug https://developer.apple.com/bug-reporting/ios/device/ (Download the iPhone Configuration Utlity to capture these logs and/or export them via Xcode/Organizer).
General notes about bugs:
• Devs should not typically expect followup unless (a) the engineer working on the issue needs more information and reaches out or (b) the/your issue has been fixed and the bug is sent back to you to please verify.
• Don't worry about category too much as the reports are checked when received and routed to the proper Engineering section involved.
• Know that devs can only see their own bugs, not those from other developers. You have access to the status of the bug, not to the bug itself. That is, you can see if it is in Analyze/Verify/Closed, not it's contents.
• For additional info, see Bug Reporting Best Practices.
• Duplicates - Understand that Apple uses 'amount of duplication' in bug reports as a way to gauge the 'severity' of an issue.
• Also note that during betas, bug reporter can be dealing with heavy loads, so be patient.
• Don't forget to go back to your bug report AFTER you submit it and set the RANK. '1' can help get it noticed asap.
Reporting Xcode Server Bugs
When reporting an Xcode Server bug, enter the following command in Terminal, then attach the output to the bug report.
sudo /Applications/Server.app/Contents/ServerRoot/usr/sbin/serverloggather
Bug Reporter Connection Issues:
• For problems connecting to the Apple Bug Reporter, let Apple know by submitting your issue via the: Connection Problems Form.
To report security issues w/Apple products: https://ssl.apple.com/support/security/
-=-
总是觉得自由地使用任何修复，样品，DOC增加，功能要求或增强你想看到报告错误。添加＃线程仅供参考，感谢您的报告。
有关错误的一般注意事项：开发者通常不应该期待后续，除非（a）工作的工程师在这个问题上需要更多的信息和到达或（二）/您的问题已被固定的bug被送回给你，请确认。此 外，开发者只能看到自己的错误。如需更多信息，请参阅问题报告的最佳实践。