iOS 6.1.3 could mark third iOS update in two weeks

iOS 6.1.3 could mark third iOS update in two weeksOh, iOS 6. In your short lifetime, you’ve kept us thoroughly entertained. I don’t think we’ll ever forget Apple’s Maps app. Amazing stuff.

On the update side of things, in the past 10 days or so, we’ve had iOS 6.1.1 for iPhone 4S owners, iOS 6.1.2, and now iOS 6.1.3 is reportedly imminent. You're really spoiling us here, Apple.

iOS 6.1.1 was specifically released for iPhone 4S users, who complained of connection problems and poor battery life on iOS 6.1. Indeed, Vodafone specifically told its iPhone 4S-owning customers not to update. Oh dear.

Following hot on its heels was iOS 6.1.2, which – somewhat surprisingly – addressed an Exchange calendar issue, which could’ve potentially affected battery life.

The more pressing issue, arguably, is the passcode bypass, giving potential hackers relatively easy access to the Contacts app, from which they can call people, export details via email, and enter the Photos app.

Well, iOS 6.1.3 is thought to plug that particular gap, with 9to5mac reporting that iOS 6.1.3 beta 2 has been rolled out to developers.

In addition to the passcode bypass security fix, there are also said to be various enhancements for Apple Maps users in Japan. Er, the four who didn’t download the iOS 6 Google Maps app.

To check for updates on iOS, tap Settings > General > Software Update.

Read more about: iOS

Add a comment
2 comments

SpartanDavie  Feb. 22, 2013 at 22:13

I'd be happy for them to update it everyday if it benefits me...

As would I be happy for my games to be updated with new levels each day :D

Besides, I imagine, like myself, most people click to update before bed and wake up to it updated so it hardly effects us...

AFB  Feb. 24, 2013 at 09:03

When all you hear is how android owners never seem to get updates, how refreshing to see a company that acts so quickly in response to its customers problems.

Email:

You don't need an account to comment. Just enter your email address. We'll keep it private.

Comment: