
Apple simply mounted a number of annoying iPhone bugs with the most recent iOS 16.3 replace
iOS 16.3 is on the market for all iPhones 8 and later with a couple of attention-grabbing options, together with bodily safety key help for Apple IDs. More importantly, it additionally incorporates a number of bug fixes and safety updates that iPhone customers have been ready for.
According to Apple’s launch notes, the iOS 16.3 replace “fixes a difficulty the place horizontal traces might quickly seem whereas waking up iPhone 14 Pro Max.” Over the previous a number of weeks, some iPhone 14 customers have complained about horizontal traces flashing throughout their screens. According to stories on social media and dialogue boards, the traces seem when the iPhone wakes up or restarts. Additionally, the discharge fixes some nagging bugs with the Lock Screen, Siri, and CarPlay:
- Addresses a difficulty the place the wallpaper might seem black on the Lock Screen
- Fixes a difficulty the place the Home Lock Screen widget doesn’t precisely show Home app standing
- Addresses a difficulty the place Siri might not reply correctly to music requests
- Resolves points the place Siri requests in CarPlay might not be understood appropriately
There are additionally a number of safety updates that would trigger main issues to your machine if left unpatched. The most regarding concerned Screen Time, Apple’s parental management and display screen administration app. According to the entry, iOS 16.3 fixes a difficulty the place an app “could possibly entry details about a consumer’s contacts.” The replace additionally features a handful of fixes that would result in arbitrary code execution.
The replace additionally will possible deliver again the brand new Home structure that beforehand arrived in iOS 16.2. Just earlier than the vacations, Apple pulled the characteristic, which improves reliability and effectivity, because of a sharing difficulty–however with out offering an replace on when it could be restored. The Home structure improve re-appeared within the second iOS 16.3 beta, suggesting that Apple has mounted the problem. However, there isn’t a point out of it within the launch notes, so it would seem in some unspecified time in the future earlier than the launch of iOS 16.4.