Disagree. I've filed bugs with trivial repro steps and have never gotten any feedback of any kind.

Even just closing them as "wontfix" would be kind.

Apple's penchant for silence or not responding shows in bug reports too. Most of the time there are no responses or changes in the status to any issues filed. Apple uses an internal tracking system for itself and an external system for anyone outside Apple, and hardly any information flows back from the internal system.

Here is the specific issue that was breaking our CI system[0]. I don't have XCode set up anywhere to see if this is still broken.

[0]: https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a...

I am fairly sure this heuristic was implemented on purpose.

Agreed; however, it ignores return value of the build step.

This logs as a warning, right? “Step produced errors even though tool exited successfully?”

no, the build step was info, not warn. It is detected as an error, and stops CI

I often did get replies, but usually they were "We've fixed it now. Simply upgrade to the new version of macOS." Of course, that wasn't necessarily true. Once, I got a whole correspondence over non-working WiFi (which they didn't resolve, but which I eventually traced to, indeed, a Trust USB-C splitter).

However, if you file bugs for Logic Pro, they get addressed rather quickly. They even take suggestions. I guess it depends on which team gets the bug.