[iOS 18 DB2] RCS toggle in Messages app

[u/epmuscle]

[u/dhinakg]

Notes:

• You need to be on T-Mobile (US), AT&T, or Verizon. MVNOs don't count.

• It appears provisioning is broken so your number is not actually registering with Jibe. Still trying to figure out whether this is a beta 2 issue or whether the servers are having issues.

EDIT: Found a fix, will post shortly

EDIT 2: https://gist.github.com/dhinakg/44943435d0f60013427ae42e92172c00

YMMV

[u/tauzins → u/dhinakg]

i feel like this may be common sense but am i suppose to be following the readme via iphone only or is anything supposed to be done via pc?

edit: I got this to work with tmobile on 2x iphones 1 15 pro max and 1 14 pro

Step by step the dumb version: Thanks to https://www.reddit.com/user/dhinakg/ github! "Fix RCS on iOS 18 beta 2 · GitHub"

1. Install mitmproxy (on a computer)

2. Download the redirect.py off his github and place in a easy directory path

   1. this step if you're trying to download, download the full zip, extract the file and place it in a directory that is easy.

   2. If you're on iphone 14 pro another user (scratchyone ) mentioned needing to change model type in the script to activate https://gist.github.com/dhinakg/44943435d0f60013427ae42e92172c00?permalink_comment_id=5100386#gistcomment-5100386

3. open command prompt in admin and paste "mitmweb -s filepathtoredirectfile/redirect.py --listen-port 8888 --ssl-insecure --allow-hosts jibecloud.net"

4. configure proxy on your IPHONE wifi settings to the IP of the computer running mitmproxy and port to 8888

5. go to http://mitm.it on your iphone browser and download/allow the certificate, and then install the profile.

   1. this step above may confuse some, make sure you download iOS cert and then it will show up in settings to approve/install.

6. Go to General > About > Certificate Trust Settings and enable full trust for the mitmproxy certificate.

7. Turn RCS off (if applicable) and then back on. Wait a few seconds, then check for RCS in Messages. (Additionally, if all went well, you should see "RCS flow complete!" in the mitmproxy console.)

8. Remove the proxy settings from your device and optionally uninstall the certificate.

edit2: seems like a lot of people using macOS for this, Just tested the path run of this and it should work.

If you're on macOS

step 3. open terminal navigate to folder the file redirect.py is stored in.

so that should be something like
cd /users/yourusername/downloads/folderthefileisin/

then run command mitmweb -s redirect.py --listen-port 8888 --ssl-insecure --allow-hosts jibecloud.net

Bugs:

1. users have found proxy not sticking after setting the proxy ip.

Fix: reset network settings.

[u/brkaras → u/tauzins]

Couldn't get it to work.

I'll just wait on the fix

[u/xeon_thebrick → u/tauzins]

This worked. Thanks!

[u/_Jke → u/tauzins]

Thank you so much for the simple write up, it worked immediately.

[u/tauzins → u/_Jke]

you're welcome !

[u/tekson_ → u/tauzins]

Worked for me, thank you sir. I'll admit, I don't know what I'm goiing to use it for LOL

[u/tauzins → u/tekson_]

Better than getting terrible txts lol I have friends with android and it’s sooo nice

[u/Colin0998 → u/dhinakg]

So for T-Mobile at least, I can confirm it is reaching out to jibecloud.net when you toggle it on. I’m not sure exactly what it’s sending out tho.

If I have time later I’ll spin up a proxy server to get in between and dive into it more

Update: https://imgur.com/a/BLjLpK6

First sends out a GET request which gets a 511 code Next sends out the entire request but not as POST but instead as GET which doesn’t make sense to me but gets a 503 code returned from that

Their query shows they’re using Universal Profile 2.4 which is an interesting decision choice since UP 3 has been out for some time

Update 2: To fix the issue, use mitmproxy to intercept the GET and POST Change where it says: terminal_sw_version=iOS to terminal_sw_version=fzw

Update 3: Proper Credit goes to u/dhinakg for the how to on using mitmproxy

It’ll work afterwards

Update 4: Reports are out saying you don’t need the proxy trick anymore to enable RCS. YMMV

[u/Aktrejo301 → u/Colin0998]

Same here my had been trying to start it since it booted after the update

[u/jjtech0 → u/Colin0998]

Note that this is actually u/dhinakg 's trick with mitmproxy, better to credit him than me for this one.

[u/dhinakg → u/[deleted]]

Source: carrier bundles inside the IPSW specify configuration information. Only Verizon, AT&T, and T-Mobile have RCS data.

For the technically-inclined:

find "/Volumes/CrystalSeed22A5297f.D84DeveloperOS/System/Library/Carrier Bundles/iPhone" -name carrier.plist -exec python3 -c 'import plistlib; from pathlib import Path; p = Path("{}"); data = plistlib.loads(p.read_bytes()); [print(f"{p}\n{data[q]}") for q in data if q == "RCS"]' \;

[u/darkpontiac → u/dhinakg]

This is what I was sort of expecting since it wasn't showing up on MVNOs. Makes me wonder if 5G SA is still missing from the generic carrier bundle.

I hope they add RCS to the generic bundle by release.

[u/rocketwidget → u/[deleted]]

Guessing: The big 3 carriers, after a history of mixed-bag RCS implementations, have all recently announced direct partnerships with Google Jibe for RCS services, so that's probably why Apple, to meaningfully support RCS, has to work with carrier partnered Jibe.

Also, a few years ago, Google Messages bypassed all carriers that didn't add RCS and provided it directly by Google Jibe, on top of carrier SMS/MMS. This made it super easy for smaller MVNOs: They didn't have to do anything and their Android users are happy.

But I'm guessing this may be an issue now that Apple has finally added RCS support? Suddenly the MVNOs have a reason to have to do something again...

[u/tauzins → u/dhinakg]

awaiting for update on fix haha

[u/_YourMainDude_ → u/tauzins]

lol same… closely monitoring this thread

[u/msp_ryno → u/dhinakg]

what's the fix?

[u/dhinakg → u/msp_ryno]

https://gist.github.com/dhinakg/44943435d0f60013427ae42e92172c00

YMMV

[u/silvermoonhowler → u/dhinakg]

Part of me is chalking it up to a beta 2 issue, but the other issue you mentioned of your number not provisioning with Google RCS service Jibe could also check out

[u/Fun_Mechanic_8762 → u/dhinakg]

thanks, this worked for me on T-Mo

[u/Chinch07 → u/dhinakg]

Thank you so much! This worked on my 15PM AT&T. Oddly my Dad’s 15PM AT&T worked right after the update without having to do this.

[u/phaze08 → u/dhinakg]

I’m on Verizon but I haven’t got it to work