Apple releases iOS 26.5 RC 2 ahead of public launch - 9to5Mac

Apple seeded the second release candidate (RC) build for iOS 26.5 and iPadOS 26.5 to developers and public beta testers today, with build number 23F77 replacing the prior RC build 23F75. The update arrives one week ahead of the expected public rollout of iOS 26.5, which is set to reach all compatible devices next week. Release candidates are intended to represent the final build that ships to end users, but Apple occasionally issues revised RCs when critical bugs are identified during pre-release testing. This second RC includes no new user-facing features, UI changes, or added functionality, focusing exclusively on stability and bug fixes discovered in the first RC testing cycle.

The first RC for iOS 26.5, build 23F75, was released two weeks ago, and entered widespread testing among developers and public beta participants. Apple's internal testing and feedback from beta users flagged several issues in that build that could affect end-user experience, prompting the revised RC 2. This pattern is not unusual for Apple: iOS 16.4 saw two RCs in 2023, and iPadOS 25.3 had a revised RC in 2025 after a bug with Stage Manager was discovered late in testing. For developers, this means the final public build of iOS 26.5 will be nearly identical to RC 2, provided no additional critical bugs are found in the next seven days.

While RC 2 itself adds no new features, the public iOS 26.5 release will include several notable additions for users and developers alike. RCS messaging now supports end-to-end encryption for compatible carriers, bringing RCS in line with iMessage's security standards. Developers building messaging apps or integrating with the iOS Messages framework can access new APIs for E2EE RCS in the iOS 26.5 SDK. Apple Maps adds a Suggested Places feature, which uses on-device machine learning to recommend locations based on a user's routine, with new MapKit APIs for developers to integrate similar suggestions into third-party navigation apps. The update also includes a Pride Luminance wallpaper, security patches, and minor performance improvements for older devices.

Developer Impact

For iOS and iPadOS developers, the release of RC 2 narrows the window to test apps against the final pre-release build before public availability. The iOS 26.5 SDK, included in Xcode 26.5 RC (available via the Apple Developer Download portal), includes headers and tools for all new iOS 26.5 features. Developers should prioritize testing apps against RC 2 for two key reasons: first, any bugs present in RC 2 will persist in the public release, and second, App Store reviewers now test submissions against the latest RC, so builds must run without crashes or major issues on 23F77.

Cross-platform developers maintaining apps for both iOS and Android will recognize this RC process: Google follows a similar pattern for Android releases, often issuing multiple RCs for major OS updates after beta feedback. For teams using cross-platform frameworks like React Native, Flutter, or .NET MAUI, the release of iOS 26.5 RC 2 means checking for framework updates that add support for new iOS 26.5 APIs. Most major cross-platform frameworks release compatibility updates within days of a new iOS SDK finalization, but testing on RC 2 ensures no regressions exist in framework-rendered components when the OS update rolls out to millions of users next week.

SDK version requirements for iOS 26.5 are straightforward: the minimum deployment target for apps using new iOS 26.5 APIs is iOS 26.5, but apps can still support older OS versions using availability checks. For example, to use the new RCS E2EE APIs, developers can wrap calls in if #available(iOS 26.5, *) { } blocks to avoid crashes on older devices. Xcode 26.5 will throw deprecation warnings for APIs removed in iOS 26.5, so developers should address these warnings in RC 2 testing to avoid App Store review rejections.

Migration Steps for Developers

Developers looking to update their test environments to iOS 26.5 RC 2 and test their apps should follow these steps:

1. Update test devices to RC 2: Ensure your test devices have the developer beta profile or public beta profile installed. Navigate to Settings > General > Software Update to download build 23F77. Verify the build number by going to Settings > General > About > iOS Version to confirm you are running the correct RC.
2. Update Xcode to 26.5 RC: Download the Xcode 26.5 release candidate from the Apple Developer portal. This version includes the iOS 26.5 SDK, which is required to build apps with iOS 26.5-specific features. Set your Xcode project's base SDK to iOS 26.5 to test against the latest APIs.
3. Test core app functionality: Run through your app's critical user flows on RC 2 devices to check for regressions caused by OS bug fixes. Pay special attention to features that interact with system frameworks like Messages, Maps, and HomeKit, as these are most likely to be affected by OS updates.
4. Test new iOS 26.5 features: If your app integrates with RCS messaging, Apple Maps, or other new 26.5 additions, test those integrations thoroughly on RC 2. Use the new MapKit Suggested Places APIs in a test environment to ensure your app handles location suggestions correctly.
5. Validate cross-platform builds: For React Native apps, update to the latest version that supports iOS 26.5, then run npx react-native run-ios --device to test on your RC 2 device. Flutter developers can run flutter build ios with the latest Flutter SDK to generate an iOS build compatible with 26.5.
6. Prepare App Store submissions: If you plan to release an app update alongside iOS 26.5 next week, submit your build for review now. App Store reviewers will test your app on RC 2, so ensure your build passes all pre-submission checks, including no crash logs on 23F77.

Apple's release of iOS 26.5 RC 2 is a standard but critical step in the OS update cycle, giving developers one last chance to fix issues before the public launch. For mobile developers maintaining apps across platforms, this testing window is essential to avoid post-launch bug reports from millions of users.