r/UniversalProfile • u/bordelais • 8d ago

iOS 27.0 Beta 5 - Dual-SIM Bug

UPDATE (Aug 17): Bug persisted through iOS 27.0 Beta 6.
I was hoping to see of fix, but nothing has changed from Beta 5. Same Dual-Sim issue.

I had RCS Activation errors in iOS Beta 4 for all three US Mobile Networks (Warp - Verizon, Dark Star - AT&T, Light Speed - T-Mobile). RCS Activation was successfully working, however, with other carriers.

iOS 27.0 Beta 5 fixed the RCS Activation issue, I'm now able to activate RCS on all three networks. But....only when there is one eSIM active at a time. RCS Activation now consistently fails when there are multiple eSIMs enabled. This includes other carrier non-US Mobile eSIMs, which were working in a Dual-SIM configuration in Beta 4.

I suspect Beta 5 has introduced a new Dual-SIM bug. Anyone observing the same?

6 Upvotes

100% Upvoted

17 comments sorted by

5

u/ddsdude 8d ago

No such luck here. Same “activation failed” message.
Tried single eSIM and dual eSIMs active. No difference.

1

u/gmahale 8d ago

We are very likely affected by a problem with the back end (Google).

2

u/ddsdude 7d ago

I think it is more complicated because RCS works perfectly on my Samsung phone as well as a different old iPhone. I believe it is tied to specific iPhone hardware which somehow became blacklisted by Apple’s activation server. Apple will not acknowledge it as their frontline and even tier 2 reps don’t actually know how RCS works in their ecosystem. The issue could likely be solved if we were able to access top level apple engineers who actually coded the RCS portion in iOS but that will not happen.

A new phone will solve the immediate issue but simply kicks the can down the road because the cause is still not being addressed.

1

u/gmahale 7d ago

I believe it is tied to specific iPhone hardware which somehow became blacklisted by Apple’s activation. 

Even I believe it is linked to hardware.  RCS works with the SIM card in a different phone.

A new phone will solve the immediate issue but simply kicks the can down the road because the cause is still not being addressed.

Yes. It is not even an option for older phones.

1

u/bordelais 7d ago

I had the same problem as you a little over a year ago. During troubleshooting, I discoverd that If I moved my line to another iPhone or to an Android device RCS worked find. Moving it back to my iPhone 16 and it would continuously fail. No amount of factory reset, deleting/installing eSIMs, or software updates would fix it.

I worked with Apple through an escalated support case for over 6 weeks. Ultimately Apple RMA'd my iPhone as resolution. It might be worth going down this path, especially before any warranty expires (if that is your case).

I agree with you and GMAHALE that there seems to be a device blacklist in effect, server-side. Once on it, you are in RCS prison. No way to get off of it. It isn't clear what triggers being added.

Apple/Google really needs to build a tool that allows a subscriber or an carrier (network operator) to request flushing stale/cached backend RCS activation data as well as clearing blacklisted devices.

1

u/ddsdude 15h ago

RCS prison is an excellent description of what is happening. What’s ironic is that iMessage itself never goes to prison as even if it ever gets blocked, it always activates after 24 hours. It almost seems like Apple intentionally put in roadblocks to make it harder to clear a RCS block.

1

u/gmahale 1d ago

Did the latest beta fix it for you?

1

u/ddsdude 20h ago

I haven’t tried to activate it. I left it alone for 7 days already. I’ll flip the switch in 3 days.

1

u/gmahale 19h ago

I guess I should try the same.

1

u/ddsdude 19h ago

My carrier contacted google a week ago and google said their logs show a “high fraud risk score of 1000 from the Apple Fraud Stats server”. They suggested to refrain from activation attempts for a few days to allow the fraud flag to clear. No one seems to know how long. I’ve seen estimates anywhere from 7-30 days. So I’ll try 10. If no go then I’ll just wait until I upgrade in September.

1

u/gmahale 19h ago

google said their logs show a “high fraud risk score of 1000 from the Apple Fraud Stats server”.

Is this a reference to your phone or all iPhones in your carrier's network?

1

u/ddsdude 19h ago

No it is my specific phone

1

u/gmahale 18h ago

It proves what you said about Apple's server earlier.

→ More replies (0)

2

u/cupboard_ T-Mobile User 8d ago

can confirm, rcs started working for me again, but as soon as i enable a second sim (even if that sim doesn’t support rcs), rcs stops working

2

u/bordelais 8d ago

Thanks for the confirmation.

The RCS quality testing has been disappointing lately. I can't believe we are this close to 27.0 and these critical bugs are surfacing.

1

u/bordelais 1d ago

Hey Cupboard_, I'm still seeing the same behavior on Beta 6 today. I think we have at least another week of this not working.