{"id":12862,"date":"2020-06-11T00:05:44","date_gmt":"2020-06-10T22:05:44","guid":{"rendered":"https:\/\/www.apfelpatient.de\/?p=12862"},"modified":"2025-02-06T08:00:54","modified_gmt":"2025-02-06T07:00:54","slug":"before-ios-14-beta-apple-explains-error-messages","status":"publish","type":"post","link":"https:\/\/www.apfelpatient.de\/en\/tipps-tricks\/vor-ios-14-beta-apple-erklaert-fehlermeldungen","title":{"rendered":"Before iOS 14 Beta: Apple explains error messages"},"content":{"rendered":"

Apple has published an article on the official developer website explaining how bugs can be reported by beta testers and regular users. <\/strong><\/p>\n\n\n\n

Apple has published a new post on the official developer website that is supposed to provide tips for error reports. It is specifically about the feedback assistant. It can be assumed that the company wants to prepare users for the upcoming iOS 14 beta - but the tip also appeals to the users of final builds among us. The article - entitled "How to submit great bug reports" - was published almost two weeks before the upcoming WWDC 2020. So it must be about the new operating systems, right? Whatever. Beta versions of iOS, iPadOS, macOS, tvOS and watchOS often contain some errors that need to be reported. But the problem is that many users don't even know how to submit error reports or how to submit such a report correctly. Apple has set up a special page for such error reports, which can be found at feedbackassistant.apple.com<\/a> can be reached.\u00a0<\/p>\n\n\n\n

Bug reports are often incomplete<\/h3>\n\n\n\n\n\n\n\n

Users of a final iOS and other versions can also submit their reports there. Beta testers, on the other hand, receive the Feedback Assistant as an app on their iPhone, iPad and Mac - provided that a beta version is actually installed on the device. But the problem is bigger than expected. Apple points out that even with the Feedback Assistant, not everyone knows how to fill out a bug report, which can make it difficult for Apple engineers to understand and fix the problem. This is what the Contribution<\/a>:<\/p>\n\n\n\n

You should always submit feedback for any bugs you find during development on Apple's platforms; after all, we can't fix problems we don't know about. But how can you be sure that the information you provide will be useful in assessing the issue and not a troubleshooting dead end? Here are some of our top tips for making sure your bug report is clear, actionable, and most importantly, fixable.<\/p><\/blockquote>\n\n\n\n

One thing is clear: the error reports must be extremely detailed and understandable. This is the only way they can be reproduced before a fix is possible. Apple points out that all steps that lead to error XY must be listed. The current result or the expected result must also be listed. <\/p>\n\n\n\n

First iOS 14 beta released at the end of the month<\/h3>\n\n\n\n\n\n\n\n

To make the report even easier to understand, users can upload both screenshots and videos via the feedback assistant. In addition, Apple explains that developers can go a step further and submit a sample project with the code that causes the problem. This would make the engineers' work much easier and significantly speed up the fixes. The post continues:<\/p>\n\n\n\n

Unfortunately, not all bugs are reproducible or have easy-to-follow steps. For trickier cases, consider providing log information like a system diagnostic: When you report a bug on your iPhone or iPad, you can use the Feedback Assistant application to capture it automatically. When you file a bug through Apple's web portal, you can install profiles that can help you capture a system diagnostic manually.<\/p><\/blockquote>\n\n\n\n

The first preview of iOS 14 and Co. is expected at the end of the month. For now, this will only be available to registered developers. A first public beta should therefore be released in July at the earliest. As soon as this is the case, I will publish an updated version of our step-by-step guide for voluntary beta testers - stay tuned and don't miss anything. (Image: Apple)<\/em><\/p>\n\n\n\n