Apple releases bug-fix update bringing iOS and iPadOS up to 13.1.3

Apple has released another incremental update for iOS 13, with the rollout of iOS 13.1.3 to currently-supported iPhones and the iPod Touch alongside iPadOS 13.1.3 for iPads and the iPad Pro.

The update, released on Tuesday, raises the version number of iOS and iPadOS by one more increment to version 13.1.3 from version 13.1.2, which Apple released on September 30. As an incremental update, the release concentrates on providing bug fixes and improvements rather than adding new features.

For iOS, the update addresses an issue that can prevent an iPhone from ringing or vibrating for an incoming call, halts a problem that can prevent a user from opening a meeting invite in Mail, and fixes the Health app where data may not display correctly following the UK clock change from British Summer Time.

The update also fixes a few iCloud Backup-related issues, including one where Voice Memo recordings may not download after a restoration, as well as a more general bug for apps that fail to download after the same procedure. For the Apple Watch, pairing issues and notification problems are also corrected.

Bluetooth is listed under two corrections, including where it disconnects for certain vehicles, while the connection reliability has been improved for Bluetooth hearing aids and headsets. Lastly, it addresses launch performance issues for apps that use Game Center.

For iPadOS, the change list is shorter, consisting of the Mail, iCloud Backup, Bluetooth, and Game Center fixes. As of yet, there are no published CVE entries for the update, suggesting there are no security-related patches being applied at this time.

Weighing in at 108.6MB for iOS upgrades from iOS 13.1.2 and 71.4MB for iPadOS, users can update to the latest iOS and iPadOS release by entering the Settings app, selecting General, Software Update, and selecting to install the update. If users have automatic updates available, this will streamline the process for them.

17 Comments

lkrupp 10521 comments · 19 Years

About 5 years ago

Even I, a committed fanboy, am starting to wonder of what use the developer and public beta programs are. One would think that developers would have the most incentive to test and report issues. As for the public betas I’m betting the percentage of public beta users actually reporting issues is very low. Most of them are just about installing something the public doesn’t have and then bragging about it. They could care less about reporting things. While I’m very glad to get updates I’m less happy about the frequency these days. Supplemental updates, to me, mean important bugs that can’t wait for the point update. That concerns me... a little.

razorpit 1793 comments · 17 Years

About 5 years ago

lkrupp said:

Even I, a committed fanboy, am starting to wonder of what use the developer and public beta programs are. One would think that developers would have the most incentive to test and report issues. As for the public betas I’m betting the percentage of public beta users actually reporting issues is very low. Most of them are just about installing something the public doesn’t have and then bragging about it. They could care less about reporting things. While I’m very glad to get updates I’m less happy about the frequency these days. Supplemental updates, to me, mean important bugs that can’t wait for the point update. That concerns me... a little.

The first few public versions of iPad OS were so bad I got tired of submitting bug reports. I spent more time submitting reports than I did actual work. That's not a good thing. A friend of mine told me told me how good it was. I'm thinking all he ever did was boot it up and get on the internet once or twice.

I know Apple probably gets pounded with bug reports from the Feedback app, but it would be nice to receive some kind of feedback from them every once in a while. There are bugs that are 2-3 years old now that remain (MacOS) that I never heard a damn thing on. Gets to the point where you have to ask yourself how often are they reviewing the feedback they do get?

esaruoho 61 comments · 12 Years

About 5 years ago

razorpit said:
There are bugs that are 2-3 years old now that remain (MacOS) that I never heard a damn thing on. Gets to the point where you have to ask yourself how often are they reviewing the feedback they do get?

I think the issue here is that while they might have a crack QA team, they have no power as they are not the magical CEO/QA/Product Owner combination that Steve Jobs was.

See a bug? Escalate it so that whoever introduced it, needs to fix it R I G H T N O W. Don't let go until it is fixed. under this CEOQAPO that Steve was, Apple had insane quality, or at least way more than right now. Now we have a non QA/testing slanted non PO guy being the CEO. That guy knows how to make money and to keep the ship going forwards. But he hasn't, as of yet, even created an Executive position for QA. Imagine that, an Executive of Quality Assurance, with the right escalating power, to cut through the siloing that seems to be going on, where teams no longer talk to eachother. Cut through the red tape, and start getting those bugs that have, more or less, been piling on since iOS7 - taken care of, right now.

This kind of EQA position needs to exist, seriously. Apple needs to stand for insane quality. That quality needs to be assured. Having an EQA with the required amount of escalation power is the only way to get back to Snow Leopard. I still love the way the software+hardware+services work, but.. seriously?

tabaks 9 comments · 5 Years

About 5 years ago

However, these updates STILL don't fix the issue where, if you lock down app deletion on iPads, that action REMOVES the Apple TV app from your device! That is such a GLARING and serious bug I'm stumped that this still wasn't fixed! What are they thinking?!

Yes, I have discussed this BUG with a senior support specialist, we've heavily documented it and included the clips of that behavior but, to no avail so far.

Fidonet127 592 comments · 5 Years

About 5 years ago

I think part of the problem is people are examining the betas so intently for the next big thing, that Apple is withholding some stuff, which means that they fork the code. That forked code is then not beta tested.