There is: https://feedbackassistant.apple.com/
That said, it isn’t very user-friendly, and I find that they don’t seem to pay much attention to it. When they do respond, it tends to be some form of “#wontfix. Please close this.”
That looks like a fairly ugly little bug. I suspect they know about it now, thanks to the HN Bug Reporter. It tends to highlight these types of things.
By not having a public record of bugs Apple conveniently hides the sheer number of them and how many people they affect.
I also submit feature requests and usability issues.
My experience is pure anecdata.
I usually end up closing the reports, after a number of months of them being ignored.
This creates an incentive for the big players to improve their process and proactively catch bugs.
I've seen bugs reported to Apple's bug reporter get fixed in subsequent OS versions, but almost never in updates to the current or previous ones. This is a fundamental flaw with their process that provides a historical track record of them deprioritizing certain bugs. Which is why we should probably pivot away from internal bug reporting services and move towards third party bug trackers.
The AAPL market cap is $3.48175 trillion as I write this.
I've had enough cases where a simple screenshot or log snippet should have been enough to accept the bug report but instead they were closed because I cannot in good conscience attach all the data they want from a Mac that I use for my day to day work.
:shrug:
If you are submitting a build for Mac (in my case, as a Mac Catalyst companion to an iOS app), you can’t reset the build number to 0, after you change the main version.
For example, if you go from 1.0.0 (106) to 1.0.1, you would expect it to be 1.0.1 (0), but it won’t let you submit a Mac build with that build. It must be 1.0.1 (107), even though the iOS build is fine, with 1.0.1 (0).
This forces me to keep updating the build number on both builds (because I sync them). I used to use the build number as an indicator of release status, but this pooches that. Not the end of the world, but annoying.
I first got a “cannot reproduce” response, where they wanted me to submit a sample app (In the original report, I actually sent them a link to my full app source code, as it is an open-source app -most of my work is open-source, and I have a number of repos that contain full source for shipping apps).
I responded, saying I would not, because it would require creating a whole fake app, with fake releases and whatnot, and it wasn’t worth it, as I had already sent them a link to a shipping app, that exhibits the problem, and also, they were quite capable of doing that, a hell of a lot more easily than I could.
I then got a second response, saying something like “Oh, I see. It is a string issue, not a numerical issue. Works as designed. #wontfix. Here’s how to close a bug.”
I gave up, and closed it.