iOS 26.5 and macOS Tahoe 26.5 release candidates are now available

Apple hardware that works with 26 generations of operating systems – Image credit: Apple

Release candidates for iOS 26.5, iPadOS 26.5, watchOS 26.5, tvOS 26.5, visionOS 26.5, and macOS Tahoe 26.5 have been released, as testing for the build nears completion.

RC builds for iOS 26.5, iPadOS 26.5, watchOS 26.5, tvOS 26.5, visionOS 26.5, and macOS Tahoe 26.5 surface after the fourth developer beta, which Apple launched on April 27. The third was released on April 20, while the second appeared on April 13.

The first round was distributed on March 30, but Apple re-released the developer beta for iOS 26.5 on March 24, with a new build number.

An RC version is usually the last before public release, but it is not guaranteed. There may be a second RC version, or even a third, depending on the behavior of the first RC instance.

  • iOS 26.5 RC 1 is 23F75, replacing 23F5069b
  • iPadOS 26.5 RC 1 is 23F75, replacing 23F5069b
  • watchOS 26.5 RC 1 is 23T570, replacing 23T5568a,
  • visionOS 26.5 RC 1 is 23O471, replacing 23O5468a
  • tvOS 26.5 RC 1 is 23L471, replacing 23L5469a
  • macOS Tahoe 26.5 RC 1 is 25F71, replacing 25F5068a
  • HomePod 26.5 RC 1 software is 23L471, replacing 23L5469a

Apple also released RC versions for its older operating systems:

  • iOS 18.7.9 RC1 is 10:35 p.m.
  • macOS 15.7.7 RC 3 is 24G720
  • macOS 14.8.7 RC 3 is 23J520

The first release of iOS 26.5 introduced notification forwarding in the EU and continued testing of end-to-end encrypted RCS messaging. However, it also accidentally introduced Apple Intelligence to China earlier than expected and did not include any Siri improvements despite speculation about the feature.

The second version laid the groundwork for adding ads to Apple Maps.

AppleInsider and Apple strongly insists that users avoid installing beta operating systems or beta software on primary devices or “critical” hardware, due to the possibility of data loss and other issues. Instead, they should keep backups of data where possible and use secondary aftermarket hardware that is not as critical to maintain in the event of a problem.

For users who want to try updates in a generally safer manner, Apple typically introduces a public beta shortly after the developer release. This is a more seasoned version of the update that tends to have fewer issues than the developer beta.

Do you find any changes in the new versions? Contact us on Twitter at @AppleInsider Or @Andrew_OSUor email Andrew at (email protected).