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.
RCS supported carriers
- Thread starter TimFL1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
One of the most important draws 'messaging' has on me (similarly in-kind with email communications) is the idea that we are effortlessly allowed to decide our response time-frames.
If I need to get an immediate response, a phone call is my choice.
When I need space to ruminate (et al.), the informal (and timeless) medium provided by messaging/email is invaluable.
I don't desire to tease the expectant respondent with an indicateur to the possibility that I've fully-completed my dissertation well-ahead of my intended publication
Involuntary {...} implies an immediacy not necessary to the convo.
I don't think I've ever heard such a complex reasoning behind messaging and a typing indicator 😂
For me the thing is easy: I do whatever I want with my messages. If others have expectations, that's their problem, not mine. I leave read receipts on, I am fine with the typing indicator. And if the person I'm typing with acts fussy because I'm not answering within 3 milliseconds, or gets upset because I'm "ignoring" them, well, then I have no interest in talking to that person.
My theory is: interaction between people should be governed by agreements between those people on a human level. We shouldn't have to resort to technical means to trick the other party of the conversation into thinking that we are not around. They need to know that it's my decision whether I *want* to be available or not.
Also, I am 47 but I may be way younger at heart, because I will never pick up a random, unplanned phone call (unless I'm sitting around super bored doing nothing). The non-asynchronous nature of phone calls is annoying and disrupts what I'm doing.
For some reason RCS between me and my best friend won’t work. It works for me and other android users. And her with other android users. Just not between me and her.
Are they only doing this for iOS 18? I hate the new photos app (I only updated to iOS 18 on my iPad not on my iPhone) but I was hoping they would add RCS to iOS 17 too
Not sure if I mentioned this already but:
there is a new theory about why some wifi networks block RCS on iOS: IPv6 support.
If your network does not support IPv6, RCS ceases to function on iOS. I verified all work wifi networks I have trouble with and what do all of them have in common? You guessed it, they only support IPv4 (can be easily checked in the individual wifi network info panel, if there is no mention of Ipv6 it doesn‘t support it).
I tried all other wifi networks I have access to (or could access today) and every single one of them that worked shows IPv6 info, all that don‘t lack IPv6.
I‘ve updated my long standing feedback with a comment outlining this theory, let‘s see if they bother doing something about it.
there is a new theory about why some wifi networks block RCS on iOS: IPv6 support.
If your network does not support IPv6, RCS ceases to function on iOS. I verified all work wifi networks I have trouble with and what do all of them have in common? You guessed it, they only support IPv4 (can be easily checked in the individual wifi network info panel, if there is no mention of Ipv6 it doesn‘t support it).
I tried all other wifi networks I have access to (or could access today) and every single one of them that worked shows IPv6 info, all that don‘t lack IPv6.
I‘ve updated my long standing feedback with a comment outlining this theory, let‘s see if they bother doing something about it.
We only have ipv4 at our other house, with WiFi calling only as there is no cell service that far out in the boonies, and RCS works..?
Yeah some other kind soul on Brandons discord destroyed my hopes of finding the silver bullet already…
I was without service all day due to the Verizon outage. Service was just restored, but RCS doesn't seem to be working. When I tap on "Carrier" in Settings > General > About, "IMS Status" now just says "Voice & SMS." RCS used to also be listed there. Anyone else having issues with RCS on Verizon after today's outage?
I apologise for any personal discomfort 🙃
Your invective-laden response begged, er, a response.
Well, there you go
This is all really high-level stuff. I have not-yet updated my devices to be RCS-aware (though I am excited to do so).
I am having trouble parsing "non-asychronous", but I think I understand what you're expressing.
Timing is everything, is it not?
Well, there you go
This is all really high-level stuff. I have not-yet updated my devices to be RCS-aware (though I am excited to do so).
I am having trouble parsing "non-asychronous", but I think I understand what you're expressing.
Timing is everything, is it not?
What I mean with "non-asynchronous" (maybe really not the proper term in this context, apologies) is that I like to be able to pick my own timing in communication. I don't want anyone to call me spontaneously, hence dictating that my flow of whatever I am doing will be interrupted in that very moment.
With messages I can decide when to answer, whenever it suits me. An incoming call doesn't give you that choice. And it ends up going like this: call rings - I reject it - I write back "hey can we talk later?" - and then having to figure out a time. Definitely quite cumbersome.
If true, that will also be a blocker to Mobile Network Operators (MNOs) why don't support dual stack...
Migrated to the 16 Pro Max yesterday and RCS service transfer was very hit and miss. Had the infamous RCS/SMS stutter for hours, seems to have stabilized over night though (fingers crossed).
I always fear the yearly phone migration, especially with iMessage. Rarely have I encountered more pain than getting my iMessage phone number registered again on the new device (usually plagued with infinite spinner until I reboot). It‘s the biggest reason why I try to only use iMessage with mail addresses, because they survive restores / migrations and never seem to get unregistered from your iMessage account…
I always fear the yearly phone migration, especially with iMessage. Rarely have I encountered more pain than getting my iMessage phone number registered again on the new device (usually plagued with infinite spinner until I reboot). It‘s the biggest reason why I try to only use iMessage with mail addresses, because they survive restores / migrations and never seem to get unregistered from your iMessage account…
I do wondering if reset iPhone without backup. I also did restore from back up when setting up iOS 18.
RCS, especially on group messaging is very unstable. You can send a message as RCS, then next one will be undeliverable. Or iOS will randomly decide to sent message as SMS. I HAVE FIVE DUPLICATED GROUP because iOS randomly decide to sent messages as SMS for whatever reason!
Last edited:
I used the wired migration feature so I don‘t have to fiddle much to get started.
I wonder when Apple updates their RCS implementation, especially changes/ fixes for RCS groups so you can‘t send MMS in there anymore …
Something funny happened: the Google Help account on Reddit contacted me, cause I ventured into the Google Messages subreddit territory to discuss RCS on iOS woes (there are quite a few people who talk about iOS 18 RCS there).
They wanted to hear about the issues I‘m experiencing, especially the wifi issues with RCS. I first thought it‘s a bait account but it‘s real and they wanted to know my iPhone model number, the timeline of when the issue popped up and any potential Apple Feedback IDs tied to the issues so that they could contact Apple and follow up about it. They seem to take RCS woes on iOS seriously and want to get engaged.
Took the time to dump more than just the wifi issues, like the group chat downgrade chaos etc. and they seem to appreciate the detailed rundown.
I‘m not naive and expect anything to come from this, but it‘s a funny incident nonetheless and glad that at least "someone" seems to care and engage with the community about RCS painpoints.
They wanted to hear about the issues I‘m experiencing, especially the wifi issues with RCS. I first thought it‘s a bait account but it‘s real and they wanted to know my iPhone model number, the timeline of when the issue popped up and any potential Apple Feedback IDs tied to the issues so that they could contact Apple and follow up about it. They seem to take RCS woes on iOS seriously and want to get engaged.
Took the time to dump more than just the wifi issues, like the group chat downgrade chaos etc. and they seem to appreciate the detailed rundown.
I‘m not naive and expect anything to come from this, but it‘s a funny incident nonetheless and glad that at least "someone" seems to care and engage with the community about RCS painpoints.
True but only EE currently have IPv6 support currently I believe so it will be some time for everyone not on EE 😉At some point - will be some time
I hope that, between Google and Apple, they work out the bugs in RCS. In the meantime, I have just turned it off. Too unreliable when I need my messaging to work. So… my primary reason for “upgrading” to iOS18 turns out to be a bust.
It’s almost like the reason why RCS is not popular is related to the networks/whatsapp and not Apple…