GrapheneOSGoogle and carriers deployed changes to RCS which have been breaking it for many users on the stock OS including with certain carriers and in whole countries. The changes appear to have specifically impacted GrapheneOS users too. It's not related to our September 8th update. We're working on it.
You can find many recent threads about people having issues with RCS in Google Messages while using a stock OS with Google Mobile Services. There are articles about how some carriers and countries no longer have it. It still works for most people but the changes definitely regressed compatibility.
GrapheneOS users were impacted by these recent changes much more than other users. We don't know why yet but we're working on determining that and restoring compatibility with Google Messages for people who use it. We'll try to get compatibility with the new way it functions implemented very soon.
xyhhx 🔻@GrapheneOS isn't RCS a standard? how is it possible to break compatibility if they're implementing a standardised protocol?
@xyhhx Not in the same sense as SMS. It has anti-spam checks and they could make it require the Play Integrity API if they wanted.
anthony@xyhhx @GrapheneOS unfortunately the decentralized, semi federated intended nature of it was undone when the carriers all gave up on serving it and switched to Google Jibe. So Google holds most of the cards and we are right back where we started with centralized messaging.