iOS 17
Apple’s third developer betas of iOS 17.4, iPadOS 17, tvOS 17.4, watchOS 10.4, and macOS Sonoma 14.4 are out now, as Apple braces itself for its big EU App Store changes.
Developers participating in Apple’s beta program can pick up new builds through the Apple Developer Center or more directly by updating their iPhone or iPad already running the betas via the Settings app. Public beta versions usually arrive a short time after the developer versions, and public participants can sign up through the Apple Beta Software Program website.
The third developer betas of iOS 17.4, iPadOS 17.4, tvOS 17.4, watchOS 10.4, and macOS Sonoma 14.4 replace the second developer betas from February 6, while the first were introduced on January 25 , January 29 for macOS .
The new iOS and iPadOS betas have build number 21E5200d, replacing the previous build, number 21E5195e. The third beta build of tvOS 10.4 is number 21L5212d, replacing the second, 21L5206f.
The third watchOS 10.4 beta has build number 21T5202e, taking over from 21T5196d. The third macOS Sonoma 14.4 build is number 23E5196e, replacing the second, 23E5191e.
The main changes in iOS 17.4 include App Store changes to comply with the European Union’s Digital Markets Act. Podcasts gain a new dialogue box icon in the lower-left corner, Music replaces Listen Now with Home, there’s an update to Stolen Device Protection, Siri updates its message-reading language support, additional game streaming app support, and new emoji round out the list.
So far, the discoveries for watchOS 10.4 include a number of new emoji characters, as well as an option to disable Double Tap on the Apple Watch when using the Apple Vision Pro due to the use of hand gestures by the headset.
Given that tvOS updates tend to involve performance improvements and bug fixes rather than features, it’s likely that the release will be in a similar vein for tvOS 17.4.
Much like its iOS counterpart, macOS Sonoma 14.4 gains support for new emoji characters.
AppleInsider and Apple strongly suggest users don’t install test operating systems or other beta or RC software on “mission-critical” or primary devices, as there is the small chance of issues that could result in the loss of data. Testers should instead use secondary or non-essential hardware and ensure they have sufficient backups of their critical data at all times.
