When you file bug reports through Apple’s Feedback Assistant, you help flag issues, improve our platforms, and elevate the experience for developers and customers alike.

You can supply more information about bugs you come across — and improve the quality of your reports — when you provide a sysdiagnose from your device and logging generated from a debug profile. Both can help engineers reproduce bugs and increase the likelihood of an issue being fixed. As always, the sooner you submit a new problem — and the more information you provide — the higher likelihood you have of getting it resolved in a future software version.

File effective bug reports

View now

Sysdiagnoses and debug profiles

Sysdiagnoses can be a crucial part of the bug-solving process. They contain logs that include additional information gathered from apps and frameworks that you can submit as part of your bug report.

That said, a sysdiagnose can contain a lot of information, and you can help the engineers triaging your issue by providing helpful context.

That’s where Apple’s Profiles and Logs page comes in: It provides supplemental instructions when reporting an issue with specific frameworks. If you think you know the framework that’s causing your problem, check its bug reporting and logging instructions; you may be able to provide additional information to help make your report more actionable.

Visit the Profiles and Logs section of the Apple Developer website to find out more about filing supplemental information for a bug.

Sometimes, a sysdiagnose is not enough, even with supplemental instruction. Debug profiles can help capture specific details about a technology or framework to aid engineers in diagnosing the problem. To install a debug profile, download it to your device from the Profiles and Logs page and follow the instructions to capture the requested information.

Learn more about Profiles and Logs

Sysdiagnoses and debug profiles are especially crucial when filing bugs against beta software, as prioritizations around fixes have to be made in early seeds. If you file a detailed bug with logs and a clear reproduction path, you have a much better chance to have your problem prioritized and fixed during the beta process.