Rosyna

anantksundaram said:

Rosyna said:

And you can downgrade for a few days/weeks after a new iOS version. 

Where have you seen this? This is the first I've heard of it. Can you please provide link?

Marvin said:

anantksundaram said:

I spent hours this weekend trying to deal with Siri not working on my Apple Watch. Went back and forth with Apple's Twitter support, then was finally sent to a live person, went through a whole series of procedures (soft reset, unpair/pair, hard reset, resync everything....), and then I was finally told (by the same live tech), a couple of hours later: "This is a known issue resulting from the iOS 9.3 update, we've got a lot of calls about it, so please wait a few days as Apple fixes this problem and issues a new update."

This is is the first time, in over three decades, I've used a swear word and slammed the phone on Apple Support.

People shouldn't have to be waiting days (it's usually weeks/months) for these things to get fixed. Apple should have a rollback system that works immediately because people are depending on these services day-to-day. If operating system updates were self-contained overrides to the core system installed, people would be able to delete the update straight away and revert back to an older working system version.

You'd start with a base system that was say 9.0. On updating to 9.1, it would leave the 9.0 base system alone and put the modifications in a separate location as overrides to the base system. Similarly 9.2 would be installed as an override of 9.1 and the base. If any update, even a beta update is going wrong, the user simply removes the update and it immediately reverts back to the last working version. There would be no downtime for users and Apple wouldn't be under pressure to fix it ASAP, they just pull the latest update and tell people who experience problems to roll it back until it's fixed. It would use a bit more space (eventually around 2-3GB) but there are ways to deal with that.

Another option would be to use a profile system instead of incremental versions. So they would maintain a profile of an OS, which would be a snapshot of all the files and program versions contained in it. Someone with an iOS device would be able to select the desired profile. Then it would check the profile already installed on the phone against a new profile and only update the changed components individually, which needs less free space. In situations like this, if the problem is just one system service, they can put a quick fix into that one system component and update an existing profile with just that change and phones that have this profile installed would detect their version of that component was out of sync and could offer to fix just that small program without having to wait on it all getting packaged up in an installer, versioned and have a support page made for it.

This kind of profiling could also be used for rollbacks so the system can replace core components with updates but store the old files in a compressed location and you'd be able to switch back. Apple would probably want to prevent people downgrading systems for security reasons but the rollback can be limited, even in real-time on their end.

ajmas said:

Rosyna said:

It has absolutely nothing to do with WebKit. It's due to the background daemon that handles links between sandboxed apps, swcd, repeatedly crashing on the bad JSON.

That could be the case, but why would it break functionality within apps?

jkichline said:

Been running iOS 9.3 beta since version 2 and performing tests and customer service for our app. Never have seen an issue. But then again I never installed this bookings.com app so I have no idea. Seems like an issue with that app but reveals something that can be improved. If bookings.com just released an update a week ago, that would explain the crashes not appearing until now.

usersinceos1 said:

If even 1000 people have this problem, out of a user base of 1,000,000,000, it comes to 1 out of 1 million. It seems that the problem might not even be attributable to Apple. Enjoy your ranting.