iOS 26.5 Release Date Settled, RCS Rollout Still Waits

iOS 26.5 release date is no longer a forecast: Apple shipped iOS 26.5 on May 11, 2026, with build 23F77, the same build it posted as Release Candidate 2 (RC, a near-final beta used for last checks) on May 8. The second candidate did not push the iPhone update into another week; it changed the signoff build and moved encrypted Rich Communication Services (RCS, the carrier-backed messaging standard that adds modern chat features to basic texts) into public beta.

The practical answer for iPhone owners is narrower. Install the update for security fixes, the Pride Luminance wallpaper, Maps Suggested Places and the new message lock icon, then check carrier support before assuming Android chats are encrypted.

The Second Candidate Became the Public Build

Apple’s developer site now lists the public iPhone release at build 23F77, matching the late Friday candidate. The first candidate, posted on May 4, carried build 23F75, so the second seed signaled that Apple had swapped bits before general release rather than moved the date.

The record matters because a second candidate can mean two very different things. Sometimes it points to a show-stopper. Here, Apple’s May 11 developer release record shows the final iPhone build followed the expected Monday window, with iPadOS, macOS, tvOS, visionOS and watchOS builds landing the same day.

That is the cleanest read on the release date question. The Friday beta did not become a one-week slip. It became the version most users were handed the following Monday.

Apple’s May Update Was Small but Not Routine

Apple’s official iPhone update notes put three user-facing changes at the top: beta end-to-end encrypted RCS in Messages, a downloadable Pride Luminance wallpaper and Suggested Places in Maps. The rest of the language is familiar Apple wording around enhancements, bug fixes and security updates.

That mix is why the release is easy to misread. It is not a broad redesign or a feature dump. For readers who want the full feature sweep, the earlier iPhone feature breakdown of encrypted RCS and Maps covers the supporting changes in more detail.

The small size still matters. Apple used a mid-cycle update to move cross-platform message privacy from promise to rollout, and that changes the test from whether the download is available to whether a specific chat shows the protection marker.

Encrypted RCS Moves the Bottleneck to Carriers

Apple’s encrypted RCS rollout notice says the feature is starting in beta for iPhone users on the new build with supported carriers and Android users on the latest version of Google Messages. The company also says users will see a lock icon when a conversation is end-to-end encrypted.

That word beta is doing work. This is not a developer-only beta in the old sense, where ordinary users should stay away. It is a public feature rollout with dependencies outside Apple’s phone software.

The message layer now has a three-party dependency: Apple’s Messages app, Google’s Messages app and the carriers on both ends of the conversation. If one side is missing support, the green bubble can still be RCS without being end-to-end encrypted.

Staggered operating-system delivery is not limited to phones. The same gap between a shipped update and an active benefit showed up in our Windows 11 update rollout analysis, where one PC could receive monthly changes before another saw the same improvement.

How to Tell If an Android Chat Is Protected

Apple’s support language gives users a simple check, but it also removes a comforting assumption. Apple’s RCS and SMS support guide says encrypted RCS can work when all participants have carriers that support encryption, and that protected conversations show Encrypted with a lock icon at the top.

• Update both ends – the iPhone needs the May build, and the Android phone needs the latest Google Messages app.
• Check both carriers – your carrier support is not enough if the other person’s carrier is missing the feature.
• Trust the lock – if the chat header does not show the encrypted indicator, assume the message is not protected in transit from third-party reading.

There is one more wrinkle. Apple says RCS activation can take a few hours, so a missing lock immediately after updating does not always prove the feature is unavailable. By the next day, the carrier list and the other phone are the more likely limits.

The Security Case Is Stronger Than the Feature Case

The privacy upgrade is the visible hook, but the security update is the better reason to install. Apple’s security content page for the May build lists fixes across components including Kernel, WebKit, Shortcuts, Wi-Fi, Screenshots and zlib, with Common Vulnerabilities and Exposures (CVE, public identifiers for disclosed security flaws) attached where possible.

Apple’s page also says the security release is available for iPhone 11 and later, along with recent iPad models. Older software tracks received their own releases on the same date, including 18.7.9 entries on Apple’s developer release page, which matters for devices that cannot move to the newest system line.

For most users, that makes the install decision simple. The RCS benefit may depend on a contact and a carrier. The security fixes do not require your friend group to have the right mix of phones.

The Release Question Now Belongs to the Lock Icon

The new gating issue is carrier coverage. Apple’s U.S. and Canada carrier feature list shows beta encrypted RCS support for major U.S. networks including AT&T, T-Mobile and Verizon, along with several mobile virtual network operators such as Mint Mobile, Metro by T-Mobile and Cricket.

The same list also shows why the rollout can feel uneven. Some entries support ordinary RCS messaging without listing the encrypted beta, and Apple says each conversation depends on both sides. That means one Android chat can show the lock while another green-bubble thread does not.

If the lock appears in the chat header, the update has done the job Apple advertised. If it does not, check the carrier list, the Android app and the person on the other end before blaming the release.