Apple’s public beta program is designed to get a larger pool of people testing the new operating system—more users, more devices, more edge cases, and hopefully a lot more feedback.
Submitting bug reports and comments to Apple is your solemn duty as a beta tester, and Apple actually listens to and responds to those reports. In fact, when we signed in to the Feedback app in the iOS 10 beta, it not only looked the same as last year’s, but also still had copies of our bug reports from testing iOS 9.
In the macOS Sierra public beta, you report issues through the Feedback Assistant app, and iOS 10 has a Feedback app too. When you install one of these betas, the app is automatically installed. If you’re unfamiliar with Feedback Assistant, we’ll walk you through the steps of using it.
Using Feedback Assistant in macOS Sierra
To launch Feedback Assistant, go to /Applications/Utilities. You’ll find an alias of it there. It actually resides in /System/Library/CoreServices/Applications, but there’s no need to navigate there when you can just use the alias.
Once you launch Feedback Assistant and continue past the intro screen, you need to log in using your Apple ID. It needs to be the same ID you used to register for the Apple Beta Software Program.
After you register, you’ll see an interface that looks a lot like the Notes app. (Ignore the message on the intro screen that says, “Help makes the next releases of iOS 9 and OS X El Capitan our best yet.”) To report an issue, click on the New Feedback button icon button next to the search bar in the second pane, or click the New Feedback button in the viewing pane (if you have no feedback selected or have selected the welcome message), or type Command-N, or select File > New Feedback.
When you create a new feedback report, you have to fill out a form. Click on the Help button on the lower left corner (the “?” icon) for guidance on how to fill out the form. You can even file reports for the El Capitan, iOS 9, and Yosemite betas by clicking on Change in the upper right and selecting the OS you want.
Don’t be afraid to be detailed in your report. Write the specific steps you took to produce the problem. Explain what you thought would happen and what actually did happen. Note down any error messages. It’s more important to explain your experience than to try and provide your own diagnosis on why there’s an issue. And don’t think that someone else has probably already filed a similar report; multiple reports of the same issue can help raise awareness for the OS developers.
Sign up for CIO Asia eNewsletters.