I enabled the debug menu to have a look at the MobileConfiguration:
- Open Google Messages (GM) and turn off RCS chats before continuing.
- In GM, Click on the magnifying/search glass at the top to perform a search
2.1 Type the following with the "*" symbol included: *xyzzy*
2.2. In a few seconds you should see "debug mode enabled" pop up on the bottom of the screen
- Go back one screen and click your picture in the upper right corner
- Select Debug
- Click RCS
- Click Configure MobileConfiguration
I have two Pixel phones, one which says "Connected", but you can't send RCS on it, if you do it fails. The "Connected" was back from before when this worked and the only thing that I needed to do was give google play services, permissions Contacts, Network, Phone, SMS as well as set:
adb shell appops set com.google.android.gms READ_DEVICE_IDENTIFIERS allow
What I discovered when looking at the MobileConfiguration was that the ACS url: [not connected] was blank, same as on my other device that is stuck at verifying, even though it says:
RCS appears to be active
Transport: Chat API w/ Tachygram
Both devices show notify_backend_rcs_is_unavailable: true. They're both on the same carrier, different eSIMs though.
3723 4098 I BugleRcsEngine: Connected state: [1], networkType: [MOBILE] [CONTEXT thread_id=23 ]
3723 4165 D BugleRcsEngine: Cannot get service version because CS.apk was not found, not pre-loaded or disabled. [CONTEXT thread_id=31 ]
3723 4165 D BugleRcsEngine: No supported version found [CONTEXT thread_id=31 ]
3723 4165 D BugleRcsEngine: Service with meta data key: JibeServiceApiVersions is not compatible. Service Version 1 is not supported. Supported versions: [] [CONTEXT thread_id=31 ]
3723 4165 D BugleRcsEngine: simId from Bugle is: redacted-pii:sim_id[chars:20,last3:509] [CONTEXT log_prefix="ProvisioningEngineDataRetriever" thread_id=31 ]
3723 4165 I BugleRcsEngine: No RCS Configuration was found in Bugle for simID: redacted-pii:sim_id[chars:20,last3:509] [CONTEXT log_prefix="ProvisioningEngineDataRetriever" thread_id=31 ]
tldr seems to be that it fails to get the RCS configuration from Tachygram.