Feedback Assistant - Apple Developer
View in English Getting started Feedback from our developer community helps us address issues, refine features, and update documentation. Please let us know when you encounter an issue with Apple software or hardware, have an SDK feature request, find code-level bugs and problems with Apple-provided APIs, or notice errors or omissions in developer documentation. Start your feedback as soon as you can. When you send new feedback, the Feedback Assistant app automatically collects time-sensitive information that’s important in helping diagnose the issue.
If you use the Feedback Assistant website, you can collect this information manually . Once this is done, you can upload the information directly to Feedback Assistant . If you plan to send feedback later or through the website, make note of key information, such as the date and time the issue happened, and collect any files or logs as soon as the issue occurs. You can start feedback on one device, save it, then switch to a different device to add more details and submit later.
File reports against beta software early. Beta software can sometimes introduce changes to APIs or new issues in your app that need to be addressed. If you encounter an issue during the beta release cycle, submit feedback right away to increase the likelihood that the issue will be addressed by the public release. Submit feedback for every issue. Even if you think an issue is obvious and are sure others have reported it, you should still submit feedback.
The more feedback we receive about an issue, the better we understand how many people are impacted by it. Using the Feedback Assistant app The Feedback Assistant app offers several helpful features: Automatic on-device diagnostics. There’s no need to manually collect and attach a sysdiagnose (diagnostic information from various parts of the operating system and all recent crash logs) for each issue. With your permission, Feedback Assistant can execute area-specific diagnostics, allowing you to send information beyond the scope of a sysdiagnose.
Remote filing. With Feedback Assistant on iPhone and iPad, you can submit feedback about your connected Apple TV, HomePod, or Apple Watch, with support for collecting device diagnostics directly on those devices. Detailed forms. Provide detailed information by answering specific, conditional questions through a simple filing process. Opening the app iPhone and iPad. On beta versions of iOS and iPadOS, the app is available by default on the Home Screen.
On publicly released versions of iOS and iPadOS, you can enable the app by installing a beta profile. The app can also be launched via the applefeedback:// URL scheme. Mac. The app is included in the CoreServices folder in all versions of macOS, and can be launched via the applefeedback:// URL scheme or by searching for Feedback Assistant in Spotlight. You can also open a Finder window and select Go to Folder from the Go menu, then enter this path: /System/Library/CoreServices/Applications.
Writing your feedback Select an appropriate starting topic. There are several places in Feedback Assistant to start your feedback. Developer Technologies & SDKs: Select this topic for feedback related to a specific framework or API, then select the specific technology (for example, CoreBluetooth) and OS (for example, iOS). Developer Tools & Resources: Select this topic for feedback related to Xcode, App Store Connect, or other developer tools and resources, then select the specific tool or resource (for example, Reality Composer Pro).
Relevant OS (iOS & iPadOS, macOS, tvOS, watchOS, or HomePod): Select the relevant OS for feedback related to general use of a system, then select the specific area (for example, Messages). File one issue per report. To ensure accurate processing, make sure your report only addresses one issue or request. Reports that discuss multiple issues aren’t actionable and may be returned for resubmission as separate reports. Title.
Your report title should be concise, while clearly describing the issue and any factors that could influence the issue you’ve encountered. Summarize and include key details, such as technology, platform, and version. For example, “Calendar events on iOS 15.2 beta are missing after creating a quick event” provides more actionable detail than “Calendar events are missing.” If the issue is related to your app, make sure to also include your app’s name and version.
Description. Your report should include instructions on how to reproduce the issue, with detailed descriptions of each step. For instance, you could write: Click Quick Event in the Calendar app. Fill out an event with any title. Press Return. Actual results: The event appears in the right place in my calendar, but then disappears. Expected results: The event should appear and stay on my calendar. After you fill in the steps and expected results, consider any additional factors that could influence the problem.
For example, are you signed into iCloud? Do you have any Accessibility settings turned on? Can you reproduce the issue elsewhere in the operating system? The more information you include, the more effectively we can diagnose the issue. Including attachments Sysdiagnose. Since the Feedback Assistant app automatically attaches a sysdiagnose for each issue, we recommend submitting reports directly from the app on your iPhone, iPad, or Mac.
A sysdiagnose contains valuable information about the state of your system and all recent crash logs, and should be included with all reports, even if you think one is not needed. Alternatively, you can use the website to manually upload relevant files and folders as compressed ZIP files. You may be asked to supply additional files after your report has been reviewed. Debug profiles and logs. You may be asked to install a debug profile so you can provide extra reporting and logging details to further diagnose your report.
Debug profiles can capture specific details about a technology or framework to help us diagnose the problem. To install a debug profile, download it to your device from the Profiles and Logs page . Then follow the instructions to capture the requested information, and make sure to include any related logs to expedite the investigation. Mac System Information Report. When you encounter crashes, kernel panics, hardware bugs, or printing issues, you must include a Mac System Information Report with your feedback.
Builds and sample code. If the problem appears in your app, consider recreating it in a smaller project so it’s easier to demonstrate. This helps narrow down the specific bug you’re dealing with and is one of the easiest ways for us to identify the problem. If you can’t produce a full project that complies, code examples are also helpful. Screenshots or screen recordings. If an issue appears in a user interface, make sure to include visuals with your feedback.
A screenshot or screen recording of the reproduced bug can provide valuable clues and details you may not have thought to include in the description field. Collaborating with your team We recommend submitting feedback from your team inbox in Feedback Assistant , where you can view all reports filed by your team, reply to comments, and send new messages to Apple. The assignee of a team report will receive a notification if there’s a request from Apple and can download any attachments or close the report at their discretion.
By default, a report is assigned to the team member who submitted it. However, it can be reassigned to any other team member. Reports from your team inbox belong to the organization rather than the people who submitted them. If an assignee leaves the organization, the report stays with the team. In addition to your team inbox, you also have a personal inbox for separate submissions. You can move reports from your personal inbox to your team inbox at any time.
What to expect after submission Your feedback will be assigned a Feedback Assi
The rest of this page is on the live site.