It’s hard to know what to make of an app update that promises to “cut crash rates in half.” If you’re a glass-half-full kind of guy, you’re happy with the increased stability. If you’re a glass-half-empty guy, though, you wonder why the hell they can’t get around to fixing the other 50 percent of unexpected software crashes.
I’m sort of a glass-half-empty kind of guy, at least when it comes to Facebook. So when they announce that their latest update to the Facebook for iPhone and iPad app has “solved a long-term mobile debugging problem and reduced the crash rate for people using the Facebook for iOS app by more than 50%,” I wonder why the hell a multibillion dollar corporation can’t fix the other half.
Apple has just reported that it has fixed a glitch that’s been plaguing app developers and downloaders today, rendering app updates downloaded today or late yesterday useless. The apps refused to launch, and no amount of re-installation would fix the issue.
Apple just issued a statement to All Things D that calls the all clear. The initial corruption was linked to Apple’s Fairplay digital rights management (DRM), and Apple said it only affected a small number of users.
It’s true: sometimes Macs do crash. More often than not, though, crashes will be limited to a single application, rather than the entire system.
You’ll know an app has crashed because it simply stops doing anything. Clicking on controls has no effect, scrolling gets you nowhere; the app simply doesn’t respond to your usual commands. So what do you do next?
First, don’t panic. OS X is designed to keep crashes under control. Even if an application has crashed, in most cases you’ll still be able to carry on just fine with work you’re doing in other applications. All you have to worry about is the one that’s crashed, and any unsaved work you had inside it.