7 ms·

"As expected, I've not heard any reply from Apple on the bug report I submitted." Does anyone ever get a reply on any bug submitted to Apple? With one excepti

"As expected, I've not heard any reply from Apple on the bug report I submitted." Does anyone ever get a reply on any bug submitted to Apple? With one exception, I get the someone else reported it or it stays open with no comments from Apple. I have only one bug they ever put the need more information generic text and that has no followup since I followed their instructions, not even a "you did it correctly, thanks".

portlander12345 11y ago
I once got a leak about a future iTunes release through a reply on Radar.
MCRed 11y ago
Yes, I've gotten requests for follow up questions, links to other bugs that mine was a duplicate of, and indications of when a particular bug would be fixed. In one case I was "doing it wrong" and I got a pointer on how to do it right.
emehrkay 11y ago
I have. I sent in a report saying that the Safari address bar autocomplete menu doesn't exit when you drag the favicon or link to another app, ultimately rendering Safari inaccessible unless you use your mouse and they asked me for a video example. I posted the video, but I haven't heard anything since. However, it is fixed now, so there is that
kalleboo 11y ago
I had a chain of correspondence on an OS X Bluetooth bug many versions back
MaysonL 11y ago
I have gotten responses for the 5 bugs I've reported.
Bud 11y ago
This isn't even a bug. It doesn't behave the way this user would prefer and the feature is not as refined as it could be. Neither of these things is a bug.
- CamperBob2 11y ago
  (Shrug) It's a terrible idea to add a feature like this without giving the user a way to turn it off. Who in the world would prefer it to work this way?
  - eli 11y ago
    You could say that about every tiny feature and then you'd have a Settings app that has thousands of options. Most people don't want that and, I think, would prefer the device to do its best to guess at the correct setting even if it gets it wrong sometimes.
    - CamperBob2 11y ago
      Tough to say in the general case, but it's often a good idea to adhere to the so-called "principle of least surprise" in UX design. If I'm riding on a trail that periodically approaches and diverges from a nearby highway, which is common around here (Seattle area), I don't want my recorded path to snap to the highway every time I exceed 12 MPH. That would come as a surprise -- an unpleasant one. I'll go so far as to say that nobody would ever expect this to happen, or be dismayed if it didn't. That's a good reason not to include a given feature, or at least to allow it to be turned off. Someone at Apple obviously thought it was a good idea, but they clearly didn't ask very many other people, or ask any cyclists at all.
    - gherkin0 11y ago
      > then you'd have a Settings app that has thousands of options However, some people would actually like that, me for instance. On Firefox, about:config is a great feature: if you know what you're doing, you can tweak any setting that's tweakable. > prefer the device to do its best to guess at the correct setting This is actually the worst of both worlds. From a UX perspective, I can understand having multiple behaviors with a setting, and I can also understand having a single behavior with no setting. However, I can't agree with having multiple behaviors that change opaquely at the whim of the machine (like in this case), which is just frustrating. At the very least, Apple should have surfaced a setting to developers to control this and made it opt-in.
Bud 11y ago
This isn't even a bug. It doesn't behave the way this user would prefer and the feature is not as refined as it could be. Neither of these things is a bug.
paxswill 11y ago
I once got a call from them on an bug I encountered with an Airport Base Station. They had me load a testing firmware on to try to reproduce the bug. I've also had a couple of bugs replied to (usually asking for more information), but these were when I was playing more with beta software.

portlander12345 11y ago

I once got a leak about a future iTunes release through a reply on Radar.

MCRed 11y ago

Yes, I've gotten requests for follow up questions, links to other bugs that mine was a duplicate of, and indications of when a particular bug would be fixed. In one case I was "doing it wrong" and I got a pointer on how to do it right.

emehrkay 11y ago

I have. I sent in a report saying that the Safari address bar autocomplete menu doesn't exit when you drag the favicon or link to another app, ultimately rendering Safari inaccessible unless you use your mouse and they asked me for a video example. I posted the video, but I haven't heard anything since. However, it is fixed now, so there is that

kalleboo 11y ago

I had a chain of correspondence on an OS X Bluetooth bug many versions back

MaysonL 11y ago

I have gotten responses for the 5 bugs I've reported.

Bud 11y ago

This isn't even a bug. It doesn't behave the way this user would prefer and the feature is not as refined as it could be. Neither of these things is a bug.

CamperBob2 11y ago
(Shrug) It's a terrible idea to add a feature like this without giving the user a way to turn it off. Who in the world would prefer it to work this way?
- eli 11y ago
  You could say that about every tiny feature and then you'd have a Settings app that has thousands of options. Most people don't want that and, I think, would prefer the device to do its best to guess at the correct setting even if it gets it wrong sometimes.
  - CamperBob2 11y ago
    Tough to say in the general case, but it's often a good idea to adhere to the so-called "principle of least surprise" in UX design. If I'm riding on a trail that periodically approaches and diverges from a nearby highway, which is common around here (Seattle area), I don't want my recorded path to snap to the highway every time I exceed 12 MPH. That would come as a surprise -- an unpleasant one. I'll go so far as to say that nobody would ever expect this to happen, or be dismayed if it didn't. That's a good reason not to include a given feature, or at least to allow it to be turned off. Someone at Apple obviously thought it was a good idea, but they clearly didn't ask very many other people, or ask any cyclists at all.
  - gherkin0 11y ago
    > then you'd have a Settings app that has thousands of options However, some people would actually like that, me for instance. On Firefox, about:config is a great feature: if you know what you're doing, you can tweak any setting that's tweakable. > prefer the device to do its best to guess at the correct setting This is actually the worst of both worlds. From a UX perspective, I can understand having multiple behaviors with a setting, and I can also understand having a single behavior with no setting. However, I can't agree with having multiple behaviors that change opaquely at the whim of the machine (like in this case), which is just frustrating. At the very least, Apple should have surfaced a setting to developers to control this and made it opt-in.

Bud 11y ago

This isn't even a bug. It doesn't behave the way this user would prefer and the feature is not as refined as it could be. Neither of these things is a bug.

paxswill 11y ago

I once got a call from them on an bug I encountered with an Airport Base Station. They had me load a testing firmware on to try to reproduce the bug. I've also had a couple of bugs replied to (usually asking for more information), but these were when I was playing more with beta software.