Second developer betas for iOS 26.6, macOS 26.6 surface

Apple’s beta testing routine for the current-gen operating systems continues, with the second developer builds of iOS 26.6, iPadOS 26.6, watchOS 26.6, tvOS 26.6, visionOS 26.6, and macOS Tahoe 26.6 out now.

The second developer builds arrive after the first, which landed on May 26.

While usually we deal with only one set of betas, sometimes we have to manage two of them. Following the WWDC keynote, Apple has introduced developer betas of its 27-generation operating systems, including iOS 27 and macOS 27.

Apple will continue to update the 26-generation operating systems as usual, complete with beta rounds running close to the fall release of the 27 generation.

• iOS 26.6 build 2 is 23G5043d, replacing 23G5028e
• iPadOS 26.6 build 2 is 23G5043d, replacing 23G5028e
• watchOS 26.6 build 2 is 23U5040d, replacing 23U5025e
• visionOS 26.6 build 2 is 23O5743c, replacing 23O5728e
• tvOS 26.6 build 2 is 23L5744d, replacing 23L5729e
• macOS Tahoe 26.6 build 2 is 25G5043d, replacing 25G5028f
• HomePod Software 26.6 build 2 is 23L5744d, replacing 23L5729e

At the same time, Apple has also brought out two more release candidates:

• macOS 15.7.8 RC 2 is 24G809
• macOS 14.8.8 RC 2 is 23J607

Generally speaking, when there are two developer beta tracks, the next-generation version will include the feature changes, while the current-gen track tends to be more muted.

Apple is keen to keep the features for the new versions. The current-gen beta updates are usually performance and security-focused.

The first iOS 26.6 beta build included a new feature for Contacts that notifies if users reach the maximum of 20,000 blocked listings. There was also a security fix for Apple Maps.

AppleInsider and Apple strongly recommend that users avoid installing beta operating systems or beta software onto “mission-critical” or primary-use hardware, due to the potential for issues and data loss. Instead, they should retain backups of their data and try to use secondary hardware that isn’t as essential to maintain.

For users wanting a less risky experience, Apple usually brings out a public beta version shortly after the developer counterpart. It is a more battle-hardened version of the update, with typically fewer issues than the developer builds.

Find any changes in the new builds? Reach out to us on Twitter at @AppleInsider or @Andrew_OSU, or send Andrew an email at [email protected].