I see this sentiment a lot amongst fellow devs that develop for Apple platforms, but it’s a self-defeating premise. A bug that goes unreported and unnoticed by

I see this sentiment a lot amongst fellow devs that develop for Apple platforms, but it’s a self-defeating premise. A bug that goes unreported and unnoticed by Apple engineers will by definition never get fixed. Whereas filing a report at least brings with it the chance that it gets fixed. Based on my own experience the majority of what I report gets fixed. I just don’t get a thank you card, or other communication in most cases, which seems to be especially a sore spot for most. I don’t really care and I wonder how realistic it is for them to reply to everyone. Their automation and triage engineers try to link duplicate reports so that an automated message goes out, regardless many will still slip through the cracks. I’m also not sure if throwing more money at the problem will noticeably improve things with the way the process is designed and the sheer volume they’re dealing with, especially since they started the public beta program and taking into account automated reporting. I personally think they should get back to the drawing board and redesign the process to one that separates some of the streams. That said, I’d suggest anyone who regularly reports to build report with relevant engineers that are active on a variety of social media, to make use of labs and other interaction moments if you’re dealing with something that affects your work because the engineers are always eager to pluck your report out of the pile and take a look and to also make use of the DTS credits you get to highlight an issue (they’ll refund you the credit once they confirm it’s a bug). I also highly recommend reading this blogpost by an ex-engineer to get a sense of what goes on behind the scenes: https://tidbits.com/2020/06/17/how-to-report-bugs-to-apple-so-they-get-fixed/ https://tidbits.com/2020/06/17/how-to-report-bugs-to-apple-s...