RCS is not even a thing in Asia. Everyone uses one 3rd party app or the other.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 18 RCS Support Rolling Out to Beta Users
- Thread starter MacRumors
- Start date
- Sort by reaction score
You forgot the PUBLIC BETA. RCS will be available to more iOS users when the public beta is released in july.
Well it's a good thing that Apple realizes the vast majority of people don't hold the belief that it's a sin against the corporation to reply to a green bubble and therefore are providing a better user experience. For the vast majority, RCS Messaging is a big improvement over SMS.
In the real world people communicate with each other regardless of the phone they use. From what I see most are happy with the improvement in texting quality and function this will provide. No matter how upset you are about this development, it's a done deal. Click the slider to shut it off and move on.
It'll still be in a beta capacity even then.
Plus, it's not like you need anything special to get the Developer Beta anymore.
I’ve have suggested a color tweak via the Feedback app. If we all do it - maybe Apple will listen.
RCS isnt controlled by carriers. Please stop spreading bad information. It runs on Vibe, which is owned by Google.
I am in a group text where I am the only iPhone and it now shows as RCS.
I am in a group text where I am the only iPhone and it is now showing as RCS for me.
RCS is absolutely controlled by the carriers just like SMS/MMS. Most of them now contract with Google to provide backend server support with Jibe, but some still run their own servers. The only way it's not controlled by the carriers is if the carrier does not offer it at all then Google Messages can connect directly to Jibe. That scenario is becoming less and less and will absolutely not be the case with the iPhone implementation.
Your carrier must support RCS for it to work with the iPhone. Most do these days and most are using Jibe to offer that support. What sort of agreement a carrier and Google have in place for data limits per image or video is anyone's guess. Whatever it is, it'll be a dramatic improvement over MMS.
Hey Google. How about enabling RCS for your own products like Google Voice? By not doing so, you reveal the disingenuous subtext behind your push for RCS integration by your rivals.
So I can only seem to get RCS working if I disable wifi and reboot.
As soon as I reconnect wifi it goes back to SMS.
Also simply turning wifi back off doors not switch back to RCS, only a reboot does.
Anyone else seeing the same?
On T-mobile in case that matters.
As soon as I reconnect wifi it goes back to SMS.
Also simply turning wifi back off doors not switch back to RCS, only a reboot does.
Anyone else seeing the same?
On T-mobile in case that matters.
FYI It sounds like Android users may need to manually enable RCS on their phones as it is not on by default.
Actually RCS is on by default now in Google Messages, however that only happened less than a year ago. Whether or not an update forced it to be switched on with an older phone or original installation of the app is a good question.
Imagine going through life like this.
If RCS isn't end-to-end encrypted (E2EE) by default, then it's a garbage fire.
Last I heard, E2EE was up to the implementation. Google's implementation may well be encrypted. Is Apple's? Frankly, in 2024 all clients need to be, and clients should refuse interoperability with non-encrypted clients. Or, better clients need to make it difficult to talk to unencrypted ones—just like web browsers and TLS.
RCS may offer modern messaging features, but those features will lull users into thinking the underlying transport is sound.
I want a super-clear warning if I'm messaging unencrypted RCS, especially in a mixed-client group chat.
Last I heard, E2EE was up to the implementation. Google's implementation may well be encrypted. Is Apple's? Frankly, in 2024 all clients need to be, and clients should refuse interoperability with non-encrypted clients. Or, better clients need to make it difficult to talk to unencrypted ones—just like web browsers and TLS.
RCS may offer modern messaging features, but those features will lull users into thinking the underlying transport is sound.
I want a super-clear warning if I'm messaging unencrypted RCS, especially in a mixed-client group chat.
It will work with group chats, but just like how every phone in the chat has to support iMessage to get iMessage features, every phone would have to support RCS to get RCS features. Since most iPhones are not on iOS 18 (and some Android phones do not enable RCS by default), RCS group chats may take a while before they become common.
Should work, the Beta 1 leaks had group chat screenshots.
It requires your carrier to push a new carrier profile that defines the RCS endpoint for Apple to use, so can take anywhere from days to years depending on how much your carrier cares about this.
Pretty much most carriers use Jibe as their backend and the UP defines the bare minimum media quality.
Only US big 3.
I believe when Apple originally announced that RCS was coming, they said they were working to get encryption into the RCS standard. Google’s implementation is not part of the standard. So hopefully it’ll come soon. SMS isn’t encrypted anyway, so we’re not losing anything.
Turning the mms and the RCS toggle on and off seems to enable it. I just sent a few messages to my cuz and I’m seeing delivered and read