4 ms·

> I would contact Apple, if there was a feedback option, but there isn’t There is: https://feedbackassistant.apple.com/ https://feedbackassistant.apple.com/ T

> I would contact Apple, if there was a feedback option, but there isn’t There is: https://feedbackassistant.apple.com/ 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.

minkles 2y ago
Conversely all 4 of the bugs I reported with that were fixed in the next minor release!
- ChrisMarshallNY 2y ago
  It may well have to do with the types of bugs I report. Many are Xcode bugs, and Xcode is one of the most productive bug farms on Earth. 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.
- chrisjj 2y ago
  RNG coding? I.e. what bugs replaced them...
- atribecalledqst 2y ago
  I reported a bug that occurs in a specific configuration of the Music app (trying to use Home Sharing + using bluetooth headphones), never heard anything back. I wonder if it's been fixed in the latest version of the OS, I still haven't upgraded...
cromka 2y ago
Every now and then I think about starting a public bug report tracker for Apple bugs since they keep theirs to themselves. The number of maddening but minuscule bugs I run into makes me wish I was using Linux again, where I can fix them myself, or at the very least report them upstream and hope someone else eventually does so. By not having a public record of bugs Apple conveniently hides the sheer number of them and how many people they affect.
- MagerValp 2y ago
  There's https://openradar.appspot.com https://openradar.appspot.com where you can at least share the bugs you file yourself.
  - hamishwhc 2y ago
    Also https://github.com/feedback-assistant/reports https://github.com/feedback-assistant/reports specifically for Feedback Assistant reports.
    - cromka 2y ago
      Also very nice. Thanks for that!
  - cromka 2y ago
    Oh, this is great! Not surprising someone already thought of it.
  - wojtczyk 2y ago
    Oh, this is great!
MagerValp 2y ago
I was also a bit surprised to read that, since Feedback Assistant.app should be the first thing that pops up if you do a spotlight search for "feedback". The app helps a bit with collecting a sysdiagnose report and makes it easy to add screenshots.
- dagmx 2y ago
  Only if you’re on beta builds afaik
  - IIsi50MHz 2y ago
    On macOS 14.6.1: 1. Cmd-Space 2. I type "Fee", "Feed", or "Feedback" 3. Feedback Assistant appears in the list of suggestions.
crossroadsguy 2y ago
It's not "not user friendly", it's criminally user hostile as a deliberate act. I know - incompetence over malice. But this is wilful malice of Apple to cover for their incompetence, so yeah maybe both. Not to mention the grand Apple opacity.
wojtczyk 2y ago
Thanks! I didn't know about this site to share feedback. I'll give it a try. Also another reader mentioned to enter Feedback Assistant in Spotlight. It's the first time I see that app.
- deergomoo 2y ago
  Honestly you might as well scream it into the nearest pillow. I'm sure someone somewhere reads some of them, but in most cases the very best you can hope for is a comment asking you to confirm whether it's still an issue in the latest release/beta.
  - wahnfrieden 2y ago
    Wasn’t it admitted or leaked through court documents that it was originally added only to placate upset users who expect to be able to submit feedback but that they weren’t going to particularly monitor or care for what gets submitted through it. I recall it was Jobs himself who didn’t want it and gave in after constant demands for a feedback contact method
    - wojtczyk 2y ago
      Thank you for the context!
zackmorris 2y ago
As a policy, I tell the world about (non-exploit) bugs from billion dollar corporations, but I report bugs directly to small businesses. 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.
- qingcharles 2y ago
  I do like single-dev apps. There are two apps I use regularly, and I have Discord open to the developers of both. They are always happy to receive bug reports (because so few report) and often open the code while I'm talking to them to figure out the problem.
st3fan 2y ago
"We cannot process this report. Please attach 50GB of logs that may or may not include PII". 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:
- ChrisMarshallNY 2y ago
  The last report I submitted, was an App Store Connect bug. 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.
ryandrake 2y ago
I got surprisingly helpful technical support through Feedback Assistant for a problem I reported having with a >10 year old Thunderbolt display. I always thought these "send feedback" forms at big companies always just went to /dev/null, but after sending three bug reports with logs (and after six months) I got a fairly technical response which was obviously written by an engineer, including a root cause diagnosis and a workaround that actually worked. Have to say I was very impressed.
Aloisius 2y ago
It appears to be fixed already in Sequoia. https://imgur.com/a/5klvt24 https://imgur.com/a/5klvt24

minkles 2y ago

Conversely all 4 of the bugs I reported with that were fixed in the next minor release!

ChrisMarshallNY 2y ago
It may well have to do with the types of bugs I report. Many are Xcode bugs, and Xcode is one of the most productive bug farms on Earth. 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.
chrisjj 2y ago
RNG coding? I.e. what bugs replaced them...
atribecalledqst 2y ago
I reported a bug that occurs in a specific configuration of the Music app (trying to use Home Sharing + using bluetooth headphones), never heard anything back. I wonder if it's been fixed in the latest version of the OS, I still haven't upgraded...

cromka 2y ago

Every now and then I think about starting a public bug report tracker for Apple bugs since they keep theirs to themselves. The number of maddening but minuscule bugs I run into makes me wish I was using Linux again, where I can fix them myself, or at the very least report them upstream and hope someone else eventually does so. By not having a public record of bugs Apple conveniently hides the sheer number of them and how many people they affect.

MagerValp 2y ago
There's https://openradar.appspot.com https://openradar.appspot.com where you can at least share the bugs you file yourself.
- hamishwhc 2y ago
  Also https://github.com/feedback-assistant/reports https://github.com/feedback-assistant/reports specifically for Feedback Assistant reports.
  - cromka 2y ago
    Also very nice. Thanks for that!
- cromka 2y ago
  Oh, this is great! Not surprising someone already thought of it.
- wojtczyk 2y ago
  Oh, this is great!

MagerValp 2y ago

I was also a bit surprised to read that, since Feedback Assistant.app should be the first thing that pops up if you do a spotlight search for "feedback". The app helps a bit with collecting a sysdiagnose report and makes it easy to add screenshots.

dagmx 2y ago
Only if you’re on beta builds afaik
- IIsi50MHz 2y ago
  On macOS 14.6.1: 1. Cmd-Space 2. I type "Fee", "Feed", or "Feedback" 3. Feedback Assistant appears in the list of suggestions.

crossroadsguy 2y ago

It's not "not user friendly", it's criminally user hostile as a deliberate act. I know - incompetence over malice. But this is wilful malice of Apple to cover for their incompetence, so yeah maybe both. Not to mention the grand Apple opacity.

wojtczyk 2y ago

Thanks! I didn't know about this site to share feedback. I'll give it a try. Also another reader mentioned to enter Feedback Assistant in Spotlight. It's the first time I see that app.

deergomoo 2y ago
Honestly you might as well scream it into the nearest pillow. I'm sure someone somewhere reads some of them, but in most cases the very best you can hope for is a comment asking you to confirm whether it's still an issue in the latest release/beta.
- wahnfrieden 2y ago
  Wasn’t it admitted or leaked through court documents that it was originally added only to placate upset users who expect to be able to submit feedback but that they weren’t going to particularly monitor or care for what gets submitted through it. I recall it was Jobs himself who didn’t want it and gave in after constant demands for a feedback contact method
  - wojtczyk 2y ago
    Thank you for the context!

zackmorris 2y ago

As a policy, I tell the world about (non-exploit) bugs from billion dollar corporations, but I report bugs directly to small businesses. 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.

qingcharles 2y ago
I do like single-dev apps. There are two apps I use regularly, and I have Discord open to the developers of both. They are always happy to receive bug reports (because so few report) and often open the code while I'm talking to them to figure out the problem.

st3fan 2y ago

"We cannot process this report. Please attach 50GB of logs that may or may not include PII". 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:

ChrisMarshallNY 2y ago
The last report I submitted, was an App Store Connect bug. 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.

ryandrake 2y ago

I got surprisingly helpful technical support through Feedback Assistant for a problem I reported having with a >10 year old Thunderbolt display. I always thought these "send feedback" forms at big companies always just went to /dev/null, but after sending three bug reports with logs (and after six months) I got a fairly technical response which was obviously written by an engineer, including a root cause diagnosis and a workaround that actually worked. Have to say I was very impressed.

Aloisius 2y ago

It appears to be fixed already in Sequoia. https://imgur.com/a/5klvt24 https://imgur.com/a/5klvt24