Forbes: Apple seeds iOS 26.5 RC2

Apple is in the last stretch of an iPhone software update, and then it blinked. On May 8, Apple pushed a second release candidate for iOS 26.5 and iPadOS 26.5, just five days after the first RC arrived on May 4. That matters because a release candidate is supposed to be the almost-final build — the one that usually goes public if nothing ugly turns up. So RC2 is a small signal, but a real one: Apple found something late enough to justify another near-finished build. (developer.apple.com) ### What did Apple actually ship? Apple shipped iOS 26.5 RC 2 and iPadOS 26.5 RC 2 to developers and public beta testers on Friday, May 8, 2026. Apple’s developer releases page lists the build as 23F77. The first RC from May 4 was build 23F75, so this is a narrow step forward, not a whole new beta cycle. ### Why does “RC2” matter? A release candidate is Apple saying, basically, “we think this is the one.” When a second RC appears, the usual read is simple — something in the first candidate needed one more fix before millions of iPhones got it. (developer.apple.com) That does not automatically mean a major delay. It usually means Apple is sanding off a late edge. ### What’s actually new in iOS 26.5? The headline features did not suddenly change with RC2. (developer.apple.com) Apple’s release notes for iOS 26.5 say the update adds end-to-end encrypted RCS messaging in beta for supported carriers, with rollout happening over time, plus a downloadable Pride Luminance wallpaper. Apple also frames the release as including enhancements, bug fixes, and security updates. (macrumors.com) ### Is encrypted RCS the big deal here? Yes — at least for regular users. RCS already made texting with Android phones less broken than old SMS, but encryption is the part that closes a privacy gap. The catch is that Apple says this works only with supported carriers and rolls out over time, so even after 26.5 goes public, not every user will see the full benefit immediately. (developer.apple.com) ### Did Apple explain what RC2 fixes? Not in a very satisfying way. Apple’s public-facing release notes for 26.5 stay broad, and the visible feature list attached to RC2 looks the same as the first RC. That usually means the change is in bug fixes, polish, compatibility, or a late-breaking issue that Apple does not spell out in consumer language. That last part is inference, but it fits how Apple handles late RC swaps. (developer.apple.com) ### Does this delay the public release? Maybe by a few days, but probably not by much. MacRumors and 9to5Mac both read the second RC as a sign that iOS 26.5 is still likely to launch next week, not slide into a long postponement. Apple has not posted a public date, so nobody should treat that as confirmed. But RC2 is usually a final tune-up, not a restart. ### What should developers and mobile teams do now? (developer.apple.com) Test against 23F77, not 23F75. If your app touches Messages-related flows, carrier behavior, subscriptions, or anything sensitive to last-minute OS fixes, this is the moment to rerun smoke tests and device checks. Apple’s own release notes point developers to the 26.5 SDK bundled with Xcode 26.5, which is the cleanest hint that the platform is nearing general release. (macrumors.com) ### So what’s the bottom line? The story is not that iOS 26.5 blew up. It’s that Apple got close enough to the finish line to call a build final, then decided one more pass was worth it. For iPhone users, that usually means the update is still near. For teams shipping apps, it means the last build that matters just changed. (developer.apple.com)