Beta program

How to Report a Beta Bug to Apple with Feedback Assistant

Running a beta and not reporting what breaks is the one part of beta testing that genuinely wastes everyone's time — including yours.

Feedback Assistant is already installed

Enrolling in either beta channel installs the Feedback Assistant app automatically. It appears on the Home screen on iPhone and iPad, and in the Applications folder on a Mac. If you cannot find it, search for "Feedback" — it is easy to miss because its icon is deliberately plain.

Sign in with the same Apple Account you enrolled with. Reports filed from a different account will not be linked to your enrolment and are much more likely to be closed without investigation.

What makes a report actionable

Apple's engineers need to reproduce a problem before they can fix it, so the most valuable thing you can provide is a reliable path to it. "Mail crashes sometimes" cannot be acted on. "Mail quits when I tap a message with an inline PDF while offline, every time" can.

Write the steps as a numbered list, state what you expected and what actually happened, and say how often it occurs. If it happens only on one of your devices, say which — that difference is frequently the clue that identifies the cause.

Attach the diagnostics

Feedback Assistant offers to capture a sysdiagnose when you file a report, and you should let it. It is a bundle of logs from around the time of the problem, and it contains the crash traces that turn a description into something a fix can be written against.

Capture it while the problem is fresh — the logs roll over, so a sysdiagnose taken two days later may not contain the event at all. Screen recordings help for anything visual, and are often the fastest way to communicate an interface bug.

Search before you file

Feedback Assistant lets you browse similar reports. Filing a duplicate is not harmful, but adding detail to an existing thread is usually more useful — particularly if you can describe a case the original reporter could not.

Duplicates do have one benefit: volume is one of the signals Apple uses to prioritise. If a bug affects you and a report already exists, filing your own with your specific configuration still adds information.

What happens next

Most reports receive no individual reply. That is normal and is not a sign the report was ignored — status changes appear against the report itself, and a bug marked as a duplicate has been linked to an existing investigation rather than dismissed.

You will sometimes get a request for more information, and responding quickly matters: an engineer is actively looking at it. Reports that go quiet after such a request are usually closed. If the problem is severe enough that you cannot keep running the beta, our exit guide covers leaving cleanly — file the report first.

Frequently Asked Questions

Where is Feedback Assistant on my iPhone?

It installs automatically when you enrol in a beta channel. Swipe down on the Home screen and search for "Feedback" — the icon is plain and easy to overlook.

Do I need a paid developer account to report bugs?

No. Beta enrolment is free for everyone now, and Feedback Assistant works with any enrolled Apple Account.

What is a sysdiagnose?

A bundle of system logs captured around the time of a problem. It contains the crash traces Apple needs to diagnose the cause, and Feedback Assistant offers to attach one automatically.

Will Apple reply to my bug report?

Usually not individually. Status updates appear on the report itself, and you will only hear directly if an engineer needs more information from you.

Related guides

Beta download guide All FAQs