Re: How do I submit bug report/enhancement requests to Apple?



David Empson wrote:
Marlon <no.spam@xxxxxxxxxxxxxxxxxxxx> wrote:


I'm aware that Apple appear to monitor their discussion forums
to find out what people are having problems with, but if you discover
something that appears to be 'wrong' (and, for instance, it's not been
'fixed' in 10.6.2!), is there a way of getting it lodged with Apple?

Bearing in mind all my stuff is out of warranty, and I have no Apple
Care, or any other contract with Apple.

Is there an ear I can bend?


There are many official methods of submitting information to Apple.

The subtle one is crash reports from your computer. They are generally
sent automatically to Apple, or you are at least asked if you want to
send them. In some cases you have an opportunity to enter some
additional text to describe the events leading up to the crash.

AppleCare can sometimes be a method to raise attention to a problem, but
I think AppleCare will direct you to the feedback page in most cases.


The main method is http://www.apple.com/feedback/ or the appropriate
feedback link within the application menu of relevant application (e.g.
iTunes).

This lets you do a "one way" feature request or bug report with little
likelihood that Apple will get back in touch with you, though they will
have enough information to contact you if they need to.


The advanced method requires that you register as a developer with
Apple. Free online membership is sufficient. Start at:

http://developer.apple.com/

Click on the Mac heading and then follow the Join procedure.

Once you have registered as a developer, you can file a bug report via:

http://bugreport.apple.com/

Filing a bug report as a developer is a more technical process. You need
to supply the bug report in a standard form with as much detail as
possible such as how to repeat the problem, expected and observed
behaviour, and may need to supply files and screen shots demonstrating
the problem.

There are also non-disclosure requirements with some aspects of being a
developer and filing bug reports.

With bugreport, Apple will assign a reference number to the bug, and
will eventually get back in touch with you in some way, e.g. if they
need more information. You can monitor the status of your reported bugs.

Most of the bugs I have filed via bugreport have been closed by Apple as
duplicates of an existing bug, i.e. someone else already reported the
same problem. In this situation, you cannot find out anything about the
earlier report.

In other cases, the outcome was that Apple either wasn't going to do
anything about the problem (e.g. a feature was deliberately removed), or
the problem was eventually fixed.


I tend to limit my use of bugreport.apple.com to bugs where I can
describe a clear set of circumstances and have a pretty good idea where
the bug is. I use www.apple.com/feedback for more general issues.

Thanks David - very comprehensive - I'll start with 'Feedback',
especially as I'm not experiencing crashes with this issue. And it is a
request that they do things how _I_ want after all :)

Cheers,
Marlon
.



Relevant Pages

  • Re: How do I submit bug report/enhancement requests to Apple?
    ... Bearing in mind all my stuff is out of warranty, and I have no Apple ... Once you have registered as a developer, you can file a bug report via: ...
    (uk.comp.sys.mac)
  • Re: Dock and stack graphics still being corrupted by running games in 10.5.3 :-(
    ... and relaunching the Dock doesn't fix it. ... set off by games that Apple STILL hasn't fixed as of 10.5.3. ... in this bug, in the hope they will apply pressure to Apple. ... DX-Ball developer is the culprit. ...
    (comp.sys.mac.system)
  • Re: nmedit on ppc64
    ... > Apple has the most slow bug report service in the entire world it seems. ... anything related to your particular bug until the fix ships. ...
    (comp.sys.mac.programmer.help)
  • Re: [BUG] New Kernel Bugs
    ... kernels before I happen to install it, discover it's broken on my own ... Given a decent bug report, I agree that having the bug not looked at is ... But what can a developer do if a bug report effectively reads ...
    (Linux-Kernel)
  • Re: [opensuse] Why am I getting 14.6G zypper.log files?
    ... to gather all the data and run the tests to jump up and go file another bug ... Would you read the bug report already? ... One developer said he didn't think it ... only to be kicked again and told *WONT FIX* that I guess I'm just getting a ...
    (SuSE)