I am not making this leap. He said he can confirm this issue is caused by the booking.com app. It's not. It might be a trigger, or it might be one of the causes. But booking.com is not THE CAUSE of this issue like he said.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Web Links Crashing Safari, Mail, Chrome, and Other Apps on iOS 9.3 [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
I am not making this leap. He said he can confirm this issue is caused by the booking.com app. It's not. It might be a trigger, or it might be one of the causes. But booking.com is not THE CAUSE of this issue like he said.
I would guess a fresh install that doesn't re-install the causing app would solve the issue. But that's a lot of inconvenience.
[doublepost=1459187891][/doublepost]
Just what we needed: more semantics.
Yeah...restore doesn't do anything to permanently fix the issue. I'm not even going through the trouble of doing a restore because it's been confirmed that the problem reappears after a short period of time.
[doublepost=1459187979][/doublepost]
It's not really semantics. It's incorrect information. People come here for answers, often creating an account for the sole purpose of finding out what is wrong with their device. Giving misinformation doesn't help anyone.
[doublepost=1459187979][/doublepost]
It's not really semantics. It's incorrect information. People come here for answers, often creating an account for the sole purpose of finding out what is wrong with their device. Giving misinformation doesn't help anyone.
It's possible, but so far a number of those who tried seemed to have mentioned the issue still being there or coming back. Now perhaps it's because some of their data got restored back through iCloud or something else of that sort, that's harder to tell. But the main point is that there is some underlying issue there that is more than just a wonky iOS install or something like that.
It's not about wonky installs. If you restore a backup, you also restore the previously-installed apps, thus bringing back the original problem. That's why I said "fresh install".
You do realize there is no way to test every permeation of apps install on people phones. Bugs happened, no matter how much testing you do. Sometimes even the smallest change can blow up stuff in ways you could never dream of happening.
So how many percentage of the approx. 800 million iOS devices in active use is affected?
Would you say less than 0,2%, like a million devices?
Does it really matter if it's ten million or half a million? It clearly is a fairly large number of devices, and it seems spread across different versions of iOS, different apps, and different generations and genres of hardware.
Since it renders the device partially unusable, it's a huge problem for each and every one of the thousands or millions affected.
It's a strange one. I've updated my iPhone 5C & iPad Air 2 to 9.3 on the first day and the iPhone remains unaffected, while iPad developed this bug on day 2 or 3 after update. Both devices have the Booking app installed, so it may not be the main reason. Waiting for Apple to fix it...
It's really quite simple.
The daemon crashes due to Condition A.
Condition A occurs in a situation that should never exist.
Crappy App B triggers Condition A due to poor authorship.
Condition A is Apple's "fault".
However, Crappy App B is the real culprit, because triggering Condition A should never actually occur.
Not sure anything really shows what the numbers or percentages are actually like. And even that aside, a million devices and thus close to that many customers affected is not significant?
Same here (except I have an iPhone 5s). Updated iPad Air 2 and iPhone 5s to iOS 9.3 last week. Have Booking.com on both devices (and used it on both devices). The iPad developed problems this morning, iPhone is still OK.
Devices that aren't affected now (through Booking.com) probably won't be, as they've changed it on their end. Devices already affected, OTOH, apparently need Apple's help to reset the corrupted database.
You mean like the boot loop I get on my Note 4 since Lollipop? Nope.
[doublepost=1459191022][/doublepost]
You won't get them. It's always Apple's fault. I've read the Apple detractors are claiming WWI was due to Steve Jobs being born in three and a half more decades.
This has been happening on my iPhone 6s and I'm hoping it's not too much longer before Apple makes an official statement and releases a fix. The wall of silence coming from Apple on this is making me more frustrated as the day goes on.
IMHO, Apple's software quality has been declining rapidly. Here's an idea: No new features for the next iOS point release. The phones have enough features. Just beta test the heck out of what's already there and release a fixed version of 9.3 as 9.4. Call it the "Snow Leopard" approach.
Then, Apple needs to completely revamp its Beta program to prevent things like this from happening in the future.
This is right up there with that iOS Update (8.0.1) which broke cellular connectivity and Touch ID.
IMHO, Apple's software quality has been declining rapidly. Here's an idea: No new features for the next iOS point release. The phones have enough features. Just beta test the heck out of what's already there and release a fixed version of 9.3 as 9.4. Call it the "Snow Leopard" approach.
Then, Apple needs to completely revamp its Beta program to prevent things like this from happening in the future.
This is right up there with that iOS Update (8.0.1) which broke cellular connectivity and Touch ID.
The history is that iOS 6 at its worst had WiFi bugs up until 6.1 that came out in January of 2013. The last release of iOS 6 was in March of 2013 to patch jailbreaks. Here we are in March of 2016, about the same time of year that iOS 6 was finished and didn't need further fixing 3 years ago. iOS 9 should be at that stage by now, and clearly it's not. Factual.
Everyone excused iOS 9's bugs a few months ago saying things along the lines of "Oh, well every X.0 release has problems!!!!!!"
We're on 9.3 and people are somehow still saying this.
What has that got to do with this thread? Your post also shows that you have run out of ideas....
Anyway, I have used all the 9.3 betas and never had this problem, but now I do. I suppose it must be a change they did in the final version. I have not installed any apps since installing the final version, nor did I change any settings.
"Free speech" and "worth writing" are not one in the same. That post was an annoying waste of comment space.
You're conflating my comment about your revised history of iOS6 with excuses for iOS9. My original comment to you had nothing to do with iOS9. It was a refutation of your comment about the stability of iOS6. It eventually became a more stable OS, but it didn't start that way.
Coupl'a things: 1. "iOS 9 should be at that stage by now, and clearly it's not. Factual." Factual doesn't mean what you think it does. That's an opinion. 2. Your keyboard may have something sticky under the 1 key. You typed an exclamation point and the key didn't lift until you had six showing. Compressed air or a wipe might help.
It sounds like Bookings was attempting to download a large dataset and then plug those values into the routing system whenever things have changed - this way they could easily add links to deep deep information as it changed without having to update the app. It wasn't until they added oh-so-many that the routing process started wavering. IMO It's the equivalent of opening Twitter and then downloading individual paths to all of the newly generated tweets since the last time - albeit on a massively much smaller scale. The deep linking system was not intended to work in this way... Of course the routing system should be able to handle apps that do this, but it takes improper usage of that system, which helps to make this bug so obscure.
I assume it'll take relaunching the Bookings app (or reinstall, or waiting, or something random) to trigger that refresh to replace the 2+mb set of routes that were cached with the newer 4kb worth of routes (and patterns, as it was supposed to be).
Beyond Apple releasing an update that fixes the issue overall and rebuilds the routing index (which happens pretty often and with iOS updates already), there's not much they can personally do at this crossroad. Maybe pull apps that exacerbate the issue? But that's kind of knee jerk so they probably won't do anything until they fix it.
I assume that the ability of an app to make a low level process this unstable is a security issue as well (memory management sucks), so they'll probably nip that in the butt.
Last edited:
Similar problems on MacOS X on my MacBook with Safari. I bet Apple messed up a daemon on both IOS and MacOS. Certain APPS and Safari are causing more or less issues depending upon how the devices are used. My four IOS devices, including two iPhones 5's are not experiencing any issues. Back to my MacBook, blank pages, tabs locking up, slow to wake in Safari (not noticed in other apps), all after update. I suspect all devices are susceptible to experiencing these problems.