A few days ago we said goodbye to this day with the appearance of a new software update from Apple: iOS 17.2.1. Even if we already knew that Cupertino was testing this version, its launch before January was quite a surprise. On another side, thereApple’s notes regarding iOS 17.2.1 revealed no news included in the update. However, in some countries, reference has been made to certain Battery related error. With these differences on the table, Apple has yet to comment or release a longer release note.
Related article:
Apple releases iOS 17.2.1 a week after iOS 17.2 release
The obscurantism behind iOS 17.2.1: battery, bug fixes and/or more
Recall that along with the launch of iOS 17.2.1, Apple continues to work on iOS 17.3, the first beta version of which reached developers last week. But now Let’s talk about iOS 17.2.1. The description of the update that reached countries like the United States or the countries that make up the European Union only says:
All users are recommended to install this update as it includes important bug fixes.
Here’s an interesting note about iOS 17.2.1 🤨🔋
The Japanese release notes mention a fix for battery drain:
“This update addresses an issue where the battery may drain quickly under certain conditions.”
Meanwhile, the English release notes don’t mention it. 🤔 pic.twitter.com/lQ192SEJp6
– Brandon Butch (@BrandonButch) December 19, 2023
The surprise came when X echoed the variations of this description in some countries like Japan where there was a completely different description:
This update includes important bug fixes and resolves an issue that could cause rapid battery drain under certain conditions.
Why is Apple reporting a battery-related change in Japan, for example, and not other countries? This is a question we cannot answer today. However, some experts suggest that this update brings significant security improvements because along with the release of iOS 17.2.1, older software like iOS 16.7.4 and iPadOS 16.7.4 were also updated . It is likely that these security errors were also present in iOS 16 and they have proceeded to fix them, especially for users who have not yet updated to iOS 17 or cannot do so.
