Apple releases iOS 17.0.3 & iPadOS 17.0.3 with overheating fixes
Apple has released updates for iOS 17.0.3 and iPadOS 17.0.3, with a key feature of the releases being fixes for an iPhone 15 overheating problem.
iPhone 15 Pro
Apple's point releases of operating systems usually include bug fixes and critical security updates that can't wait for the next full release. Unusually for a point release, we know what it's fixing.
Apple confirmed on September 30 that an update was on the way for iOS 17, following reports of iPhone 15 handsets overheating. While blaming third-party apps like Instagram for some of the trouble, Apple also admitted to finding a bug in iOS 17 and that it would be addressed in a future software update.
The release of iOS 17.0.3 and iPadOS 17.0.3 follows after iOS 17.0.2 and iPadOS 17.0.2 from September 26.
The new releases have build number 21A360, replacing the 17.0.2 builds, number 21A351.
Anyone running iOS 17 or iPadOS 17 on the affected devices are encouraged to update as soon as is reasonable. Performing a backup before updates is highly recommended.
Read on AppleInsider
Comments
No
No
No
Try Apple Support….
iPhone 14 pro max I own is still overheating, when no apps are running (except in background I suppose) Phone gets hot in my pocket since OS 17.
My friends 15 pro max was never overheating! Weird.
My problem is NOT FIXED.
battery drain = heat generated
Apple has focused only on the latter because here we are talking about the “perceived” overheating. A slow, continuous but excessive power drain would most likely not be noticed as overheating by the user.
This self corrected for me after about a day after the initial 17.0 update.
I'd say that in the past it would be unusual to see so many updates rolled out so quickly because doing releases used to be a lot more work and more costly. They probably would have waited a little longer and accumulated more bug fixes before releasing a bigger update. Today, a lot of software development organizations follow a continuous integration/continuous delivery (CI/CD or simply CD) model which, in theory, means that every build or every daily build is in a releasable state. In other words, if they had to ship the daily build, it would be good to go and fully tested. That's the goal, but I'm not sure Apple or very many software development organizations hit that goal perfectly. Getting closer to the goal still represents a significant improvement.
For CD to work software development organizations have to use a lot more automation, especially around regression testing, but in all aspects of their process from compilation, understanding dependencies impacted by code changes, code signing, integration, version control, change management, installation packaging, etc. There are usually still some processes that require manual testing and verification, but anything that can be reliably and predictably automated without sacrificing the fidelity of the entire software system or introducing variation helps speed up the process is fair game for automation.
So the simple answer is: because they've made the whole update process easier, faster, and less risky they can release far more often without sacrificing quality. While we are annoyed by the frequency of these updates, we are now exposed to the negative side effects of bugs for much shorter periods of time. In a world of zero day security exploits, this model has become a necessity for survival. This is why Apple has spent a great deal of effort on refining their CD process to the point where they can support their Rapid Security Response (RSR) update model. So far, so good. But like everything software related, it's still not perfect. Perhaps AI will help move us closer to perfect.