{"id":239100,"date":"2025-10-20T17:49:10","date_gmt":"2025-10-20T17:49:10","guid":{"rendered":"https:\/\/www.newsbeep.com\/us\/239100\/"},"modified":"2025-10-20T17:49:10","modified_gmt":"2025-10-20T17:49:10","slug":"these-key-messages-upgrades-are-still-missing-from-ios-26-at-least-for-now","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/us\/239100\/","title":{"rendered":"These key Messages upgrades are still missing from iOS 26, at least for now"},"content":{"rendered":"

\t\"\"<\/p>\n

Earlier this year, Apple confirmed <\/a>that it\u2019d be supporting end-to-end encryption with RCS in a future software update. At the time, iOS 18 was still the latest version of iOS \u2013 thus implying that the upgrade would come as part of the next round of software \u2013 iOS 26.<\/p>\n

So far, end-to-end encryption is yet to ship. That\u2019s not the only thing though. The upgrade to end-to-end encryption would\u2019ve also necessitated other major upgrades<\/a> to the RCS protocol, and as of iOS 26.1 beta, it\u2019s all still missing.<\/p>\n

End-to-end encryption<\/p>\n

For reference, Apple shipped the most barebones version of the RCS protocol when they released it with iOS 18 last year. They utilized version 2.4, which only handled the basics \u2013 like read receipts, higher quality photos, and typing indicators. It didn\u2019t have any sort of end-to-end encryption at launch, primarily because the open RCS standard didn\u2019t have it yet \u2013 not until version 3.0.<\/p>\n

In March, Apple confirmed<\/a> to 9to5Mac that they\u2019d be supporting RCS end-to-end encryption, just shortly after the release of RCS version 3.0:<\/p>\n

End-to-end encryption is a powerful privacy and security technology that iMessage has supported since the beginning, and now we are pleased to have helped lead a cross industry effort to bring end-to-end encryption to the RCS Universal Profile published by the GSMA. We will add support for end-to-end encrypted RCS messages to iOS, iPadOS, macOS, and watchOS in future software updates.<\/p>\n

While end-to-end encryption is the key thing Apple highlights with RCS version 3.0, there\u2019s a number of other new features that RCS on iPhone will gain as part of the upgrade.<\/p>\n

RCS 2.7 upgrades<\/p>\n

As mentioned prior, iOS currently utilizes RCS version 2.4. With RCS version 2.7<\/a>, the protocol implemented a number of massive upgrades, bringing it more in par<\/a> with other modern texting platforms, such as iMessage:<\/p>\n

In-line replies<\/p>\n

Proper support for reactions<\/p>\n

Custom reactions<\/p>\n

Ability to edit messages<\/p>\n

Ability to delete\/recall messages<\/p>\n

As of now, RCS on iPhone does support reactions, though not properly. Currently, it\u2019s simply parsing a fallback text that says something along the lines of \u2018User added x reaction to message\u2019 \u2013 rather than properly handling an emoji reaction.<\/p>\n

Beyond that, the ability to edit, delete, and in-line reply to messages between iPhone and Android will be a huge plus. There\u2019s still no timeline on when these upgrades should be expected, other than the fact that they\u2019ll likely be part of the iOS 26 release cycle.<\/p>\n

Given the fact that these upgrades aren\u2019t currently supported in iOS 26.1 beta, the next earliest window is likely iOS 26.2, set to debut around December. Only time will tell when RCS version 3.0 will actually arrive.<\/p>\n

My favorite Apple accessory recommendations:<\/p>\n

Follow Michael:\u00a0X\/Twitter<\/a>,\u00a0Bluesky<\/a>,\u00a0Instagram<\/a><\/p>\n

\t\t\t\t
\n\t\t\t\"Add
\n\t\t\t\"Add
\n\t\t<\/a><\/p>\n

FTC: We use income earning auto affiliate links. More.<\/a><\/p>\n

\"\"<\/a>\t\t\t\t