Apple seeds 26.5 release candidates

Apple just moved its next round of platform updates into release-candidate territory — basically the “this is probably the final build” stage before public rollout. On May 4, Apple posted RC builds for iOS 26.5, iPadOS 26.5, macOS 26.5, watchOS 26.5, tvOS 26.5, visionOS 26.5, and Xcode 26.5. That matters for regular users because the public release is usually close after an RC. But it matters even more for IT teams, because this is the moment to find the weird management bug before thousands of devices update at once. (developer.apple.com) ### What exactly shipped? Apple’s developer releases page shows the full RC slate dated May 4, 2026. The build numbers are already there too — iOS and iPadOS 26.5 RC are 23F75, macOS 26.5 RC is 25F71, watchOS 26.5 RC is 23T570, tvOS 26.5 RC is 23L471, visionOS 26.5 RC is 23O471, and Xcode 26.5 RC is 17F42. That is Apple saying, in effect, “test this now, because we’re close.” (developer.apple.com) ### Why does “release candidate” matter? A beta can still move around a lot. An RC usually means Apple thinks the build is ready for general release unless something serious breaks. You can see the timing here too — Apple seeded the RC about a week after beta 4 for iOS 26.5 and iPadOS 26.5, which is a pretty classic end-of-cycle pattern. So if you manage fleets, you should treat this as the dress rehearsal, not just another beta. (macrumors.com) ### What’s actually new for users? The headline feature looks like end-to-end encrypted RCS messaging in the Messages app. That is the big one because it closes a long-standing gap in iPhone-to-Android texting — richer messaging had arrived, but strong default privacy for RCS conversations was still missing. Reports tied to the RC also point to a new Pride-themed wallpa(macrumors.com) broadest real-world impact. (9to5mac.com) ### Why should enterprise admins care now? Because Apple’s device-management world has been shifting underneath them. Microsoft says Apple deprecated legacy MDM-based software update commands and payloads with iOS 26, iPadOS 26, and macOS 26. Intune’s current guidance is to manage Apple updates through Declarative Device M(9to5mac.com)mpatibility checkpoint for update rings, compliance timing, and enrollment assumptions. (learn.microsoft.com) ### What should teams test first? Start with software update enforcement. Intune’s Apple guidance now centers on two DDM styles — “latest version” and “targeted version” policies — with deadlines, delays, and autonomous enforcement on device. So the smart test list is boring but important: supervised enrollment, ADE flows, update deferrals, deadline behavior, us(learn.microsoft.com) behavior still exists. (learn.microsoft.com) ### Is this really a next-week release? Apple has not, from what’s visible in the release pages, posted a public date yet. But RC status is usually the tell. The best inference is that public releases are close unless Apple finds a blocker in the final validation window. That is why the admin window is narrow — not because Apple issued a warning memo, but because the calendar does. (developer.apple.com) ### What’s the bottom line? The real news is not just “Apple shipped another beta.” It’s that Apple’s 26.5 cycle is effectively at the finish line, and the combination of near-final builds plus Apple’s DDM transition makes this a practical test moment for anyone running managed Apple devices at scale. If something in your fleet is going to break, better this week than rollout day. (developer.apple.com)