Existing users, 
From George Warner at Apple:
Our (Apple's) official policy is that we don't support APE'd systems. Period. The data miner that parses all the crash logs that are sent to us automatically ignores any report that has APE api's in the backtraces or dylb lists.
Likewise If DTS receives a crash incident with API in the backtrace or dylb list we will not investigate it. Our "standard answer" in this case is to inform the developer that we don't support APE and that we'll only be able to help them if they can reproduce the problem without APE installed.
Application Enhancer
Modify system apps through "haxie" patches.
Version: 2.5.2
Apple's APE policy
Feedback Type: Commentary
Contributed by: sjk Thursday, March 15 2007 @ 11:30 AM PDT
Product Platform: MacOSX
Used Product For: Have Not Tried
Recommend Product: NO
Comments
Apple's APE policy - sjk
I understand what you mean though Firewire's not the best example since it's bundled with the OS; APE isn't. Obviously Apple doesn't want any responsibility for differentiating between potential and actual APE-related issues. I'd like to know where they've drawn the lines with other third-party software; is every Input Manager, QuickTime extension, etc. on their verboten support list?Friday, March 16 2007 @ 02:05 PM PDT
Apple's APE policy - greatcow951
Well, Firewire appears in every crash report I see that is sent to Apple. Does this also mean that Firewire is no longer supported by Apple also? I ask this simply because that the idea of blaming every crash on one item (APE) is ludicrous unless you're capable of proving it.Reply to This
Thursday, March 15 2007 @ 07:02 PM PDT