File Apple bug reports on iPhone, iPad or Mac

June is the best time of year to give feedback to Apple on betas for iPhone, Mac, iPad and Apple Watch. Just after the company releases the initial betas of its upcoming software updates, this is when Apple engineers have the most time to address bugs and make changes. And that makes this the optimal time to file Apple bug reports.

It won’t be long before Apple coders’ task lists fill up through the fall, when the new software will be released. After that, teams are rearranged to make the sprint toward the next year’s Worldwide Developers Conference.

How do you file a bug report or send in feedback on iPhone or Mac? Apple made a tool called Feedback Assistant that will guide you through the process. It’s available if you’re running a developer or a public beta of iOS, macOS or iPadOS.

So if you have any input, you’d best make yourself heard now.

How to file bug reports and feedback to Apple

Ready to report bugs to Apple developers? Just open the Feedback app on your iPhone or iPad or Feedback Assistant on Mac. You’ll need to sign in with your Apple ID. Then tap the New Feedback button.

You’ll see a list of categories. As an end user, you’ll probably pick from the first five items (iOS & iPadOS, macOS, tvOS, watchOS and HomePod). The others are for developers, enterprise device managers and accessory-makers.

Next, you need to write a title for your Apple bug report. You want the title to be short and precise, like a headline. You might naturally describe an issue like, “If I don’t have the Contacts app installed, I can’t get an AirDrop of a contact card.” However, you’d want to title your feedback, “Cannot receive contact over AirDrop without Contacts app installed.”

Think carefully about how you categorize your feedback

The next question you will see is one of the most important: “Which area are you seeing an issue with?” In the preceding example, the feedback could be filed under either AirDrop or Contacts.

There are a few forces at play behind the scenes. Apple’s engineers will take any excuse to say, “This feedback doesn’t apply to us, I’m going to close it.” So you definitely don’t want to categorize your Apple bug report incorrectly. On the other hand, if you assign a feedback to a category with a skeleton crew of three people, like Game Center or Calendar, your feedback is like one more body in the 2-mile-long iPhone line.

Back to the example, both AirDrop and Contacts might be fully staffed, especially if both apps received new headlining features this year. So for this example, I’m going to file my Apple bug report under Contacts.

Now, you need to select what type of feedback you’re reporting:

• Incorrect/Unexpected Behavior is Apple’s euphemism for a bug. Something goes wrong inside the app while you’re using it, or doesn’t work as it should.
• Application Crash is self-explanatory — you’re using the app when it suddenly disappears and drops you to the iPhone Home Screen with no warning or animation.
• Application Slow/Unresponsive is for when things seem to be functioning as intended, but the app feels slow, jittery or doesn’t react to your touch.
• Battery Life is a catch-all for complaints about an app degrading your battery life.
• Suggestion is for tips and ideas. Apple’s engineers read these, allegedly, but few receive any attention.

Write a good description

In the next section, you want to describe how to re-create the problem as precisely as you can. See if you can get the bug to happen again if you do the same thing. Also, see if you can set up a situation where it doesn’t happen. The more information you can put in this box, the better. Step-by-step instructions are as good as gold when filing an Apple bug report.

At the very least, retrace your steps. Outline what you were doing before the bad or unexpected behavior happened in as much detail as possible.

If you want to attach screenshots or screen recordings, tap Add Attachment. It’ll only be seen by Apple Developer Relations and relayed to Apple engineers, but you should still censor any personally revealing content inside the screenshot if possible. A sysdiagnose — an automatically generated report on the state of the device — will be attached to the feedback. This report of various system settings will help in the debugging process if necessary.

Once you get everything finalized, tap Submit to send in your feedback.

Be sure to follow up on your Apple bug report

There are a few things you should know after you submit your bug report:

• Your feedback will be relayed through Apple’s Developer Relations system. Any replies you put on the feedback with follow-up or new information is not guaranteed to be passed along to the engineers who are actually tasked with handling it.
• If you make an important discovery after submitting the feedback, don’t bother replying to your original report. File a fresh feedback with all the information in one place.
• If it’s a truly catastrophic bug that’s afflicting you, submitting the same feedback again immediately after Apple releases a new beta might help. Apple pays special attention to bugs that are filed around that time.
• If you are blessed with a response, you need to file a reply as soon as possible. Often, if you don’t respond within a few days of testing on the latest developer beta, Apple will consider the issue resolved.

You just might be lucky enough to have your bugs and feedback addressed before the month is over if you follow all these tips. If that happens, buy a lottery ticket and take me to Vegas while you’re at it.

We originally published this post on how to file Apple bug reports on June 14, 2023. We updated the information.