Apple Feedbacks are an avenue to report anything from bugs and issues to requests for new or improved functionality. Regarding the enterprise and school IT space, Apple Feedbacks are crucial to getting various bugs fixed, and letting Apple know what could be improved with managing devices.
As the MDM provider, Addigy is unable to submit feedbacks on your behalf, and we may ask you to submit an Apple Feedback if an issue or feature request is identified as something that can only be addressed by Apple.
This article will cover some parts from Apple's own write-up on Apple Feedbacks, as well as some general tips.
What to Expect from a Feedback
If a member of Addigy identified the request as one that must be addressed by Apple, and an Apple Feedback is suggested, there are a few important things to understand.
Apple Feedback is not expected to provide immediate support, as there is no set SLA as with a standard support team. Rather, it is to be used as a way to inform Apple of a bug, issue, or requests for various improvements. When submitting a feedback, an Apple engineer will review it whenever possible and begin their investigation (if needed).
In the case of requests that ask to add new or improved behavior or functionality, Apple may deny the request or let you know it is planned in a future release.
In the case of issues and bugs, an Apple engineer will likely investigate further, and if it's deemed a bug and a possible fix is identified, they will let you know.
How to Submit Apple Feedback
To submit a feedback, you can either use the on-device Feedback Assistant app or the Feedback Assistant website.
You will be asked to sign in, and the Apple Account you use is very important. You should use your Managed Apple Account associated with your Apple Business/Apple School Manager instance, as this helps identify that you are filing as part of an enterprise/school entity, and not just a regular consumer.
Once you are signed in, you can click New Feedback on the right-hand side:
From there, choose the applicable topic. If this is for a request that is OS agnostic, choose Enterprise & Education.
In the next screen, note the following:
- Title. Make sure your title is descriptive of the issue and not something like "Problem with Apple Business". You should aim to give a good idea of the problem, without being overly wordy. For example, "Apple Business - Migration Deadline feature not selectable for known supported devices".
- Problem Area. Be sure to designate the applicable problem area, as this greatly helps speed up the overall feedback process. If you are unable to identify the problem area, we suggest using "Device Management".
- Description. Your report should include a more in-depth explanation of the issue/request, and instructions on how to reproduce the issue, with detailed descriptions of each step.
-
Sysdiagnose. Sysdiagnose logs are extremely important to help Apple identify what could be causing the issue you are reporting. A feedback regarding a potential bug should almost always be submitted with relevant sysdiagnose, especially for cases that are not easily reproducible.
- If you have a ticket with the Addigy support team, we may have these sysdiagnose logs and should be able to provide them to you. If sysdiagnose logs must be gathered through other means, please review the article corresponding to the device type.
Gathering a sysdiagnose File on Affected Hardware (macOS)
Gathering a Sysdiagnose from an iPadOS or iOS device - You can add sysdiagnose from a different device by selecting Add Attachment > Choose File...
If you are submitting feedback from the Feedback Assistant app, be sure to remove the automatically attached logs from your device.
- If you have a ticket with the Addigy support team, we may have these sysdiagnose logs and should be able to provide them to you. If sysdiagnose logs must be gathered through other means, please review the article corresponding to the device type.
Help with Workarounds
Per Apple, workarounds may be available within the feedback itself, or you can search/ask about a possible workaround on the Apple Developer Forums.
We highly suggest joining the MacAdmins Slack and joining the private #appleseed-private channel, as other members of the MacAdmins space could also be experiencing the issue and may have discovered a workaround. The steps for joining this private channel can be seen in the pinned messages of the public #appleseed channel.