WWDC Lab More Useful Than Feedback
Bugs are an inevitable part of the development process. Though they can be frustrating to bump up against, you can help squash these sorts of problems quickly by identifying the issue you’re running into, reproducing it, and filing a bug report through Apple’s Feedback Assistant.
[…]
You should always file feedback for any bugs you find while developing for Apple platforms; after all, we can’t fix problems we don’t know about. But how can you be sure that the information you provide is helpful for triaging the issue, rather than a bug-solving dead end? Here are our top tips for making sure your bug report is clear, actionable, and — most importantly — fixable.
Casey Liss (tweet, Hacker News):
Very quickly upon getting to work on my new computer, I realized that things weren’t working properly on this new machine. After some research, it appeared that some aspects of the Vision Framework were not available on Apple Silicon based Macs.
[…]
In the roughly 225 days since I filed that feedback, I received precisely zero… well… feedback.
[…]
I didn’t expect much to come of this [WWDC] lab[…]
[…]
Having my problem worked around, in the span of five minutes, with a single-line code change is both delightful and incredibly frustrating.
Frustrating because he took the time to file a good bug report with no response, frustrating because labs are only available once a year and not everyone can get in to one, frustrating because Apple was already aware of the bug but had neither fixed it nor documented the workaround.
Previously:
- Getting Feedback to Apple
- The Sad State of Logging Bugs for Apple
- Reporting Bugs as External Developers
- File Radars Early and Often
Really sad.
Are Tech Support Incidents to actually do anything? I had a show stopper bug with AppleScript in the early ARM days (no source for an email???) and did a Tech Support Incidents. The result was the usual crickets.