Apps on iPhone 5s crashing at twice the rate (2%) as on iPhone 5, iPhone 5c (1%)

“Whenever there is a new operating system, it’s not surprising to see apps crash at a somewhat higher rate, given all the changes,” Ina Fried reports for AllThingsD.

“But one of the interesting things in Apple’s latest iPhone transition is that apps appear to be crashing at a much higher rate on the new iPhone 5s as on either the iPhone 5c or the iPhone 5,” Fried reports. “In its look at hundreds of millions of app launches since the debut of the latest iPhones, Crittercism says that programs crash about two percent on the iPhone 5s, as compared to just under one percent on both the iPhone 5c and iPhone 5.”

Fried reports, “Crittercism CEO Andrew Levy said… that perhaps the reason… [is that] developers were able to check their apps for compatibility with iOS 7 during several months of beta testing, the new hardware [64-bit A7 chip and an M7 co-processor] wasn’t available ahead of time.”

Read more in the full article here.

MacDailyNews Take: Each version of iOS 7 improves the already low crash rates on the 64-bit iPhone 5s. There are a lot of changes with the iPhone 5s and Apple has done and is doing a magnificent job with a transition this big.

44 Comments

      1. MacFreek, were you born an asshole, or have you been practicing assiduously to achieve your current stratospheric level of asshole-ness?
        Just curious, it’s rare to come across someone who goes out of their way to piss off so many people, so much of the time, I wondered if it was congenital.

      1. And that is what some don’t seem to grasp; if you have almost no crashes at all even a tiny amount of crashes represent a large increase (like 100%) but still represents a tiny amount of crashes.
        Kind of like saying by buying two lottery tickets you chance of winning the lottery have increased 100%. They still however, even after doubling, would represent a tiny, tiny fraction of one percent.

  1. iOS 7 obliterates battery life on an iPad even when settings are adjusted to minimize background processes.

    I have seen iPads fully charged, all background processes killed and put to sleep that drop most of their battery capacity in an hour or two. Offline- no display- no apps running, just not powered completely off.

    The same iPads under iOS 6 could stay in the same state all day plus.

    That is not sweating the details.

    1. Haven’t changed any settings on my ipad, no battery issues.

      My iPhone 5 did.. But I think it was the battery itself starting to go.
      I had that “lock button stopped working” hardware issue with it, apple gave me a new iPhone 5. Battery life seems good now.

    2. My iPad, on the contrary, runs just the same as it did with iOS 6, as does my iPhone 5, and my iPhone 4.
      The ONLY app that appears to have an issue is Shazam, which occasionally does a weird flickering thing on starting up, and produces an error message about an audio problem, but still tags the song. I can’t say I’ve had any issues with any other app, although the pad did run out of juice the other night, when it thought it still had >30% or so left! and wouldn’t power up! I had to do a hard re-set, but I couldn’t swear that power hadn’t dropped below 5%, I was watching TV, while browsing stuff as well; I probably wasn’t paying attention.

    3. I do Daily use of a average of 3 hours a day and I charge my ipad 3 about every 3-4 days. I haven’t noticed any difference with ios7. Except more features. Sucks but maybe a restore to new May help? The battery issues seems to happen with every update for a different groups of people it seems. Glad I haven’t been one.. Yet. I do try to let the battery completely drain once a month (give or take) and let it charge up completely.
      On the crashing issue, it’s happened to my 5s a few times so far but it seems to be when I’m listening to iTunes Radio. Usually when I switch to ITR from another app. It’ll crashes to the apple logo.
      One good thing I noticed with the 5s, as soon as the phone boots up past the apple logo, the iPhone is ready 100%. My 5 and every phone under that would take a few extra seconds to find network. Then it would lag until it did. Now as soon as it’s up, I’m unlocking and doing whatever with no lag. Just a simple thing. But I like.

      1. Gonna reply to myself here but I thought app crashes were when the phone reboots. Thinking about it after reading other comments, I can see that they are different and why. Dumb mistake on my end.
        So I’ve gotten a few phone crashes on my 5s. No app crashes like the headline says. My phone goes to the black screen and the apple. It just happened again about a hour ago. Like the ones before, it was when I was multitasking back to iTunes Radio from another app while listening to I tunes radio. Soon as I touch the page and it blows up it goes black.
        Not even close to every time. But maybe 5 times since launch. And I listen to iTunes Radio quite a bit.
        This was the 1st iPhone since the 3GS that I did as a new phone. To get rid of apps I just couldn’t delete. So shouldn’t need a factory restore I’d think.

  2. I have had even native apps, mail for example, crash on every attempt to open a message or send a new message. Has happened multiple times. Had to hard rest the iPhone 5s to get mail to function. Same with other apps.

    Even worse I have had the entire phone reboot spontaneously. In some cases trying to open an app like safari. But this week the phone was sitting on a table next me and I happened to glance at it and saw that it just rebooted, the Apple logo popped up and the phone restarted.

    Looks like I need to go to the local Apple store and talk about a replacement.

    1. Call support! Whatever is happening is not normal, I’m sure they can help. My recent experience with phone support was fantastic. Just guessing but it sounds like you need to backup and restore, I have not experienced any crashes on mail or Safari.

  3. Since the departure of Scott Forstall iOS hasn’t felt the same. It has lost its unique identity among the pantheon of mobile operating systems. It now looks like another generic made-in-Korea OS that attempts to mimic Samsung TouchWiz, albeit unsuccessfully.

    Since loading iOS 7 on my iPad, it feels more sluggish, apps crash more often, and iBooks loses its pagination if you leave it open and switch to another app before switching back again. iOS 7 has this unpolished feel to it that makes it look like a sophomore effort, not a graduate student’s.

    Someone should tell Cook to swallow his pride and bring back Scott Forstall to instil some qualitative standards back to iOS 7. I’ll leave that to Carl Icahn in his monthly meeting with Cook to beat some sense into him. Ive obviously isn’t cutting it as a software designer.

      1. No, it shouldn’t. His opinion is just as valid as yours. In fact, he also states his impressions with accuracy. You, as usual, offer only pathetic personal attacks, and offer no evidence whatsoever that Bull is mistaken in any way. That makes you the loser in this debate.

    1. Stock is up now, only a couple hours later.

      Your comment was outdated the moment it was written and completely useless to anyone. Focusing on the moment-to-moment movements of a stock is pretty stupid to begin with, in my opinion, but if I wanted know this stuff, I would look at a stock ticker that updates in real time.

  4. I’ve had my 5S for 3 weeks and during that time I’ve had exactly one app crash. It happened last night and it was the Camera. No biggie. Started right up again.

    But I have also noticed that Siri takes longer to answer since I installed the iOS update. Anyone else having that issue?

    1. Mine is hit or miss. Like always, but it hits way more then it use to. The problem I have with siri is when I’m working and I receive a text, then I ask her to read it to me, she talks super fast. The 1st time I thought someone text me like a school girl. With all of the abbreviations like–OMG did u c ur bla bla bla. Ttyl crap. I could not understand her and still can’t most the times. She takes no pause between words. I use the beat tours. Not the best but far from the cheap.
      I even went into accessibility settings to where you can choose how slow or fast siri’s reads what it is I highlighted, but it doesn’t work for when I press the button. If it’s more then 2 sentences I gotta see the phone to see what was said. A pain with dirty hands.
      I even asked her to slow down. Lol. I don’t know what she said. Probably a bing search of “Siri slow down when you talk.”

  5. I love all my Apple products, but I as well have seen my iphone 5s restart for no reason 2 times now. Also my 3rd gen. iPad is running slow on ios7. Keys react so slow sometimes it’s hard to type anything. Also my fingerprint scanner did not work on day one. Apple engineers looked at the problem and sent me to the Apple store for a new iPhone. They actually told me over the phone that it was their first time hearing of the problem. But as usual Apple did the right thing and have me a new iPhone.

  6. How can anyone be encouraged by the flood of people claiming that they only experienced one or two crashes?

    Can someone truly articulate an acceptable excuse for an app that works on iOS6 to work poorly or crash on iOS7?

    What do you think Jobs would have told the iOS development team if he experienced multiple crashes?

    Sorry, but this is only one of many issues that indicates that Apple is not sweating the details like it used to. Lowering standards and legitimizing failures are things MS fans would do. I can’t believe Apple users here would give Cook & Co a free pass. Admit it, Apple’s software development these last few years leaves a LOT to be desired. Moreover, Apple’s refusal to easily allow users to revert back to iOS6 is just pathetic.

    … oh, and does anyone want to buy iWork ’09 in 2013? You would think Apple would have the resources to do a better job and offer MUCH more timely software releases.

    1. …indicates that Apple is not sweating the details like it used to

      As I point out below, problems of this sort are NOTHING new. Also, Apple frequently has gaps in their ‘sweating the details’. I vividly recall the efforts from 2007 – 2009 to shame Apple into getting serious about OS X security. It was carried out by a bunch of hackers who pointed out the problems and provided loads of proof-of-concept malware to hammer their point. Eventually Apple responded to the point where it is extremely hard to establish a botnet or mass infection on Macs specifically because of Apple’s current attention to malware. (XProtect, Gatekeeper, tightened user permissions, etc.)

      IOW: Apple is never perfect, always better than the alternatives. But every now and then Apple requires a good swift KICK to get off their butts and solve an important problem. Tim Cook’s presence hasn’t changed a thing in this respect.

      1. I suppose you’re right, Derek, but remember that 8 years ago Apple was still a massive underdog with limited resources. Today it has no realistic resource constraints whatsoever. Standards at Apple should be better than ever, and the first person who should answer for the many obvious quality issues is Cook himself. Obviously axing Forstall didn’t cure anything in Cupertino, the lethargy goes all the way to the top.

        Daniel, thanks for the words of encouragement. We know all too well that MDN is littered with obnoxious fanboys who attempt pathetic personal attacks against those who have legitimate objective criticism of their beloved company, not realizing that it is people like us who continually goad Apple into improving. Sadly, Cook appears to be managing iOS by feature comparison to Android, not by technical excellence in response to user input.

        1. but remember that 8 years ago Apple was still a massive underdog with limited resources

          Absolutely.

          Believe me, I’m no advocate for letting sleeping dogs lie when it comes to quality business. Just this past week I created a ruckus over at the iTunes/Mac App store because one of their reps blew off, in a very kind and gently worded way, my request for support by sending me to AppleCare, which has NOTHING to do with iTunes/Mac App Store support. Thankfully the rep responded by sending my complaint up the chain of command. But the last time I had to deal with those bozos I ended up letting Apple Customer Care loose on them to get them to actually DO something for their customers. That was during the Jobs era.

          So PLEASE continue goading Apple into improving. As I attempted to illustrate with my reminiscences about hackers bashing on Apple to get serious about security, giving Apple a swift kick is sometimes the best method of getting something done over there. That’s been a perennial situation.

          Regarding iOS: I have to agree with you. SImply meeting parity with some Android original ideas is NOT what I expect of Apple. ‘Good enough’ has never been an Apple mantra and it’s NOT good enough for me. Etc. 😀

  7. Zero problems with iOS 7 on 4- iPhone 5s, 2 iPads, 2 iPad mini.

    Have about 230 different apps on each. iPads are 128Gb and I have movies, presentations and lots of documents and not one problem.

    No crashes. What I did do is restart after first installing iOS 7 and each update. Beyond the restart of the install. Maybe that is a key. Not sure.

    I guess I live in iOS Heaven. 😉

  8. Since I updated my iPhone 5 to iOS 7.x, I have frequent problems launching the AppStore – it mostly just quits upon launching. Upon doing some research, I found 4 different workarounds for the problem; turns out there’s a shit ton of people with the same problem. Just sayin’.

  9. This is ‘Version 1.0 Syndrome’, which, sadly, is normal in our current era of software coding. I’m going to bet that most of these crashes are due to bad memory management code.

    Sending Apple feedback is best squeak to get them to grease the wheel.

  10. iOS 7 is a significant update from bottom to top – the user interface is the most noticeabke change, but the move to 64 bit and the support for the M7 processor is much more significant. Developers have lots of extra APIs to consider as well. Beta testing helps to get most of the bugs ironed out, but in a device which relies so heavily on third party apps it is virtually impossible to test every situation.

    A machine crash can be caused by any number of issues – ditto for slow performance or battery consumption. If you want to debug the problem you need to remove all apps, reload the OS and test the device for performance, battery life and stability before loading any apps. You only need one badly behaved third party app to mess things up.

    As for 5s crashes being more frequent than 5 crashes, before you draw any conclusions from this you need to know whether the 5 is running iOS7 (not stated in the MDN excerpt and I haven’t read the whole article) and whether the crashes occur on a “virgin” device without 3rd party apps. You also need to know what wireless hardware is in use – third party wireless routers may not conform to latest standards, and may not be running latest software.

    Problem solving in the tech world means careful, painstaking, removal of variables. Most end users have neither the patience nor the know-how to do this effectively, so the statistics quoted in this article are essentially meaningless.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.