Report error to apple

Feedback Assistant for Developers

Developer feedback is vital to making the Apple ecosystem even better. With Feedback Assistant available on iPhone, iPad, Mac, and the web, it’s easy to submit effective bug reports and request enhancements to APIs and tools.

Using Feedback Assistant

You can submit feedback to Apple using the native Feedback Assistant app on iPhone, iPad, and Mac, or the Feedback Assistant website. When you submit feedback, you’ll receive a Feedback ID to track the submission within the app or on the website.

Feedback Assistant App

The Feedback Assistant app for iOS and macOS includes several convenient features:

Automatic on-device diagnostics. There’s no need to manually collect and attach a sysdiagnose for each bug. With your permission, Feedback Assistant can also execute area-specific diagnostics, allowing you to send information beyond the scope of a sysdiagnose.

Remote filing. With Feedback Assistant on iOS, you can file reports about your connected Apple TV, HomePod, or Apple Watch, with support for collecting device diagnostics directly on those devices.

More detailed forms. You can provide detailed information through specific, conditional questions while still enjoying a concise filing experience.

More feedback statuses. You’ll have a better understanding of the statuses of most feedback you’ve filed.

Installing the App

The app requires iOS 12.4 or later, iPadOS 13 or later, or macOS Catalina or later. 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. All versions of macOS include the app in /System/Library/CoreServices/Applications, and it can be launched with Spotlight or the URL scheme applefeedback://. When enrolling a macOS system in beta builds with the Beta Access Utility, the app is added to the Dock and aliased in /Utilities.

Attaching Screenshots, Profiles, and Logs

Since the Feedback Assistant app automatically attaches a sysdiagnose for each bug, we recommend submitting bug reports directly from the app on your iOS device or Mac. Alternatively, you can use the website to manually upload relevant files as well as folders as compressed file archives. To compress a folder on Mac, right-click or Control-click on the folder and choose Compress from the menu that appears.

Be sure to include any necessary profiles and logs to expedite our investigation process. A Mac System Information Report is required for crashes or kernel panics, reports against hardware, and issues with printing. After reviewing your report we may ask for additional files, which you can attach after submission.

Sharing Feedback with Your Team

You can automatically view and respond to feedback filed by your team members if you’re part of an organization in the Apple Developer Program, the Apple Developer Enterprise Program, Apple School Manager, or Apple Business Manager. Simply sign in to Feedback Assistant with the same credentials. Current assignees and the roles listed below are able to re-assign and close feedback, and download attachments. These roles can also remove feedback from the team inbox.

Program Roles: Account Holder, Admin, App Manager

Apple School Manager and Apple Business Manager Roles: Site Manager, Admin

In addition to your team inbox, you’ll also have a personal inbox for separate submissions. You can move feedback into your team inbox if you wish.

This feature in the Feedback Assistant app requires iOS 14, iPadOS 14, or macOS Big Sur.

Viewing Older Bug Reports

While Apple Bug Reporter is no longer available, you can still track your older bug reports in Feedback Assistant using their associated Problem IDs. Bugs are displayed in Feedback Assistant, with the original text and attached files included. The Problem ID is appended to the title and any dialogue is displayed natively in Feedback Assistant as messages from Apple and replies from you, complete with timestamps.

As part of our commitment to privacy and to address the European Union’s General Data Protection Regulation (GDPR), we’ve removed developer data from certain bug reports as of late fall of 2018.

Data was removed from inactive bugs. Bugs that have been closed for at least five years, have not been updated for 60 days, and are not a duplicate of another bug had developer data removed. Developer-originated sysdiagnoses and related attachments were deleted, and any reference to the bug originator were redacted. In addition, these bugs are no longer displayed.

Duplicate bugs will remain available for a limited time. If a bug is marked as a duplicate, developer data will be removed once the original bug has been closed for five years and has not been updated for 60 days. Until then, you can continue to follow the state of the original bug until it’s closed, and engineering can still reach out to you until the bug is resolved.

Requesting Support

You should file a bug report if you continue to experience an issue with Apple software or services. For support-related issues, contact us.

Program Support. For help with your developer account such as changing your name, changing your address, or inviting people to your development team, contact Apple Developer Support.

Technical Support. If you are an Apple Developer Program member, you can request code-level support. Submit a Technical Support Incident (TSI) after filing the bug report. Your incident will be assigned to a developer technical support engineer who can provide a workaround if one is available. For up-and-running support, contact AppleCare.

Submitting General Feedback

If you’re not a developer and would like to provide feedback on public beta versions of Apple software, you can use Feedback Assistant as a member of the Apple Beta Software Program.

Источник

Apple объяснила, как правильно сообщать о багах и проблемах с iPhone и iOS

Apple выпустила инструкцию, в которой рассказывается, как правильно сообщать компании о различных проблемах с айфонами и прошивками.

Всякий раз, когда вы регистрируете новый отчет об ошибке, будьте понятны и показывайте все наглядно. Предоставляете ли вы конкретные отзывы об ошибке, с которой сталкиваетесь, или общие отзывы — опишите вашу проблему подробно.

1. Все начинается с четкого заголовка. Он должен содержать емкое описание проблемы. Например, «события календаря в macOS 10.15.4 отсутствуют после создания быстрого события».

Плохо: «Отсутствуют события в календаре».

2. Если вы разрабатываете приложение, то укажите в описании и заголовке его название и версию сборки.

3. При описании своей проблемы тщательно расписывайте каждый шаг. Часто бывает полезно сделать вид, что тот, кто его читает, никогда не видел приложение или систему, о которой вы сообщаете.

Например, если вы напишете «Когда я создаю событие в Календаре, оно исчезает через мгновение», на экране недостаточно подробностей, чтобы воспроизвести проблему. Вы создаете событие календаря с помощью кнопки «Быстрое событие» или перетаскиваете, чтобы добавить новое событие? Как долго длится момент? Событие исчезло после выхода из многозадачности или вы остались в программе?

Вместо этого подумайте, как можно подробно описать свою проблему. Например:

• Нажмите кнопку «Быстрое событие» в приложении «Календарь».
• Заполните событие с любым названием.
• Нажмите «Создать событие».

Фактический результат: событие появляется в нужном месте календаре, но затем исчезает.

Ожидаемый результат: событие календаря должно появиться и остаться в моем календаре.

После заполнения ваших шагов воспроизведения и ожидаемого результата также стоит рассмотреть дополнительные факторы, которые могут повлиять на проблему.

• Вы вошли в iCloud?
• У вас есть какие-либо настройки специальных возможностей?
• Воспроизводится ли проблема подобным образом в других местах ОС?

4. Воспроизведите проблему и сделайте скриншоты или видеозапись экрана. Последнее особенно полезно, чтобы разработчики могли посмотреть все тщательно и, возможно, обнаружить ошибку, которую вы не заметили.

5. Укажите в баг-репорте логи ошибок. Для этого в сервисе создания отчетов есть специальная клавиша.

Источник

How to File a Bug Report with Apple Directly

Though the Mac is fairly error free and tends to run much more stable than some of the competitors out there, many of us will find a bug or two in day to day usage anyway.

Sometimes the bugs are minor, sometimes they’re fairly major and can dramatically impact how Mac OS X or iOS works or behaves.

Bugs are just a reality of software development, but that doesn’t mean we as end users can’t do or say anything about it.

If you’re like me and have run into some unusual quirks and bugs in iOS and Mac OS X lately, and based on conversation with other Mac users I know I’m not the only one here, it’s fairly easy to let Apple know what’s going on.

Instead of just complaining about it (or writing a post about it, like this!), it’s much more helpful to Apple and the Mac community to file a bug report directly with Apple.

How to File a Bug Report Directly to Apple

To file a bug report with Apple, you can easily fill out an online form here:

You’ll want to fill out the entire form, describe how to reproduce the bug and what it does, attach a few files to support the bug case if possible, and offer any other additional bug details that may be necessary or helpful.

You’ll need an ADC (Apple Developer) login to use the bug reporting tool, I imagine this is a requirement to insure that bug reports are filed by relatively qualified technical people. But guess what? Anyone can make a Apple Developer login, you don’t have to be a paying developing in the iOS or Mac developer programs to file bug reports. So if you stumble upon something which is definitely a bug, do everyone a favor and file a bug report with Apple!

Don’t want to file a bug report but just want to voice your opinion on an Apple product or service? You can do that too, through the official Apple feedback channels here.

Источник

How to fix «App Store Connect Operation ERROR ITMS-90771»

I’m trying to submit my app to TestFlight, but I keep getting this error.

and this is what I have in my info.plist

How do I fix this?

4 Answers 4

Add this in your info.plist and then resubmit your app

or if you use more than one BGTask then use this code

Or Even Better:

As it says you need to add «BGTaskSchedulerPermittedIdentifiers» to your info.plist. You have turned on background task capabilities for your app but did not add corresponding identifiers.

1. Goto your Info.plist file. Hover over any item + button will be highlighted. Click on it to add a new item.
2. Copy and paste «BGTaskSchedulerPermittedIdentifiers» under the Information Property List column. This will create an array in the Type column.
3. Click the add button on the item you just created to add background task identifiers for the array.
4. Note that it is recommended by apple to mention task background task identifier in reverse domain notation(com.something.name).

In the end, it will look like this,

For more info, you can refer to this Apple doc.

Источник