aoude
I think all of us on this message thread share the same frustration.
However, in my personal opinion, all of my frustration is directed at Google. They created the RCS system, tried to shove it down everybody's throats, and then once got partial adoption, backed off and made individual carriers take over the implementation in a discoordinated and piecemeal fashion.
Most egregiously, the way they designed it, you cannot easily deregister from the RCS server, and you experience the problem that you have with people trying to add you to a group, but it still tries to send it to RCS.
De-registering takes 30 days, if it even works at all, and during that time you obviously can miss crucial messages.
All of this, in my mind, lands squarely at the feet of Google, a trillion dollar company that easily could have done it differently.
While I'm sure the Google software developers don't like making a product with this huge of a flaw, it would not surprise me if some MBA-types in the Google C-Suite don't mind that Google Messages is the only app in the world that works with RCS --thereby locking you into their product.
While some people consider it a flaw of GrapheneOS that RCS messages doesn't work out of the box -- I personally consider that to be a byproduct of successfully doing what the GrapheneOS mission is:
preventing Google Play Services from running with elevated privileges and having access to every bit and byte of your personal Android device.
While I hope some permanent workaround can be found, I don't hold it against the developers of GrapheneOS that they have not been able to put out the dumpster fire that Google created.
You may have noticed that the only other software in the world that partially works with RCS is iMessage made by Apple, another trillion dollar company.
Incidentally, when I switched to GrapheneOS from iPhone a few years ago, there were a few group chats on iMessage that never made it to me on android MMS -- despite de-registering my phone number with Apple