DevJuice: If you don't report the bug in the beta to Apple, it does not exist
To paraphrase some Apple employees: "Radar or GTFO." As many Apple persons are pointing out this week, unless you report bugs (called "radars") to Apple, you are doing nothing to improve the circumstances of which you complain.
As Chris Rawson has pointed out repeatedly over the years, Apple's "beta" releases are what normal people would refer to as alpha. On a good day. If they're feeling generous.
Apple offers a simple guide as to whether you should or should not file a bug report: the answer is always Yes.
Beta participants are encouraged to file radars even when the issue seems trivial, only happened once, seems "obvious", or may be a dupe.
Duplicates are never a bad thing -- they're like casting a vote. Highly duplicated items appear on manager reports, and various versions contain bits of information that add to the whole.
I speak from experience. Apple employees posting on the developer forums may swat you with large trouts to encourage you to comply with filing radars.
I should also point out that bug titles are editable, you should explain the bug in the field called "description", and if Apple calls you (hint the phone numbers start with 408, specifically 408-996-1010, and will be more likely this week after WWDC if you talked with an evangelist or engineer), you should probably answer the call.
Want to learn more? Visit the WWDC videos page (credentials required) and watch Maximizing Apple Developer Resources.
Don't forget to check out Open Radar, the developer crowd-sourced site for non-beta bugs.
Subscribe to Newsletter
Software Updatesmore updates
- Pandora Radio 5.1: Wake up to your favorite station
- Microsoft revamps Bing for iPad
- Plex updated for iOS 7
- Readdle rolls out PDF Expert 5: iCloud support, shared folder with Documents by Readdle
- FlightTrack 5: new look and features just in time for holiday travel
- HBO Go for iOS update adds Google Chromecast support