Following the discharge of a second launch candidate late final week, Apple will launch the first main replace to iOS 17 on Monday or Tuesday. Whereas early iOS updates often carry a slew of latest options, this replace will solely carry a few small enhancements to AirDrop and Apple Music. However the largest cause to hurry to replace can be quite a few bug fixes.
Apple already mounted a few widespread points with a flurry of small updates to iOS 17, however this launch will repair quite a few nagging bugs which have new and outdated iPhones alike. Among the many fixes, based on Apple’s launch notes, are the next:
- Fixes a difficulty which will trigger the Important Location privateness setting to reset when transferring an Apple Watch or pairing it for the primary time.
- Resolves a difficulty the place the names of incoming callers might not seem when you find yourself on one other name.
- Addresses a difficulty the place customized and bought ringtones might not seem as choices in your textual content tone.
- Fixes a difficulty which will trigger the keyboard to be much less responsive.
- Fixes a difficulty which will trigger show picture persistence.
That final repair is probably the most notable, as quite a few studies across the internet have claimed “burn-in” points with the iPhone 15. Some have swapped out their gadgets at Apple Shops solely to have the identical concern pop up. Burn-in is feasible with OLED shows however hardly ever occurs after only some weeks of use.
Apple nonetheless has a number of iOS 17 options but to be launched, together with the brand new Journal app, however it’s good that iOS 17.1 can be extra of a upkeep replace. Since iOS 17 launched in September, there have been numerous studies of issues, a handful of which had been mounted with the iOS 17.0.1, 17.0.2, and 17.0.3 updates.
It has been reported that one other widespread concern, the place telephones are randomly restarting in a single day, has not been mounted as of the newest beta. It’s attainable that Apple will shortly push a smaller iOS 17.1.1 to deal with that bug.
