RCS Between iPhone and Android Not Working? Fix Missing Features, Photos, and Group Chats

When a message from an iPhone arrives on Android as an ordinary text, or a family group loses its typing indicators after someone changes phones, the reason is not always a broken messaging app. Three systems can be involved: iMessage, RCS, and SMS/MMS. They have different requirements, different fallback behavior, and different capabilities. Understanding which one is carrying the conversation is the quickest route to a fix.

First identify the type of message

On an iPhone, a blue bubble generally means iMessage. Green means the message is being sent through RCS or SMS/MMS; green alone does not prove that RCS has failed. Apple says RCS can carry higher-resolution photos and videos, delivery and read receipts, typing indicators, and messages over Wi-Fi or mobile data, subject to carrier support. Older SMS lacks most of those features; MMS can carry media but often compresses it heavily.

In Google Messages, look at the compose field or conversation details and the RCS status in the app settings. A chat that has fallen back to SMS may still send short messages perfectly while images, group behavior, and read receipts change. Test one-to-one text, a photo, and a group message separately; they do not always fail for the same reason.

Check whether your carrier supports RCS on iPhone

Apple requires iOS 18 or later and a mobile plan with a carrier that supports RCS on iPhone. The availability is determined by region and provider; owning a recent iPhone is not enough. On iPhone, open Settings > Apps > Messages > RCS Messaging. If that switch is missing, check the carrier's current feature support rather than reinstalling Messages or changing random network settings.

If the switch is available, turn it on and allow activation time. Restarting can help after a SIM change or carrier-settings update, but avoid toggling it over and over during an activation attempt. Apple also permits a choice of default SMS/MMS/RCS app on supported versions; confirm the messaging app you actually intend to use.

Confirm the Android phone is registered for RCS

On an Android phone using Google Messages, make it the default SMS app, then open its profile menu, Messages settings > RCS chats. Check the current status, not just the toggle. Google's troubleshooting guidance calls out carrier restrictions, Internet availability, and the ability to receive SMS during setup. Verification sometimes needs a valid working phone number and mobile service even though future RCS chats can travel over Wi-Fi.

If the screen says the carrier disabled RCS, that is a carrier issue. If it remains stuck verifying, check the number associated with the SIM/eSIM, mobile data, SMS reception, and whether the phone recently changed its default messaging app. Google advises against repeatedly disabling RCS because it can remove you from existing RCS group conversations.

Wi-Fi works for RCS, but SMS still has a role

RCS relies on data connectivity. SMS ordinarily relies on the cellular messaging service; Apple notes exceptions where SMS can use Wi-Fi Calling. Test with Wi-Fi and mobile data independently. If texts arrive only when mobile service is available, determine whether the conversation is truly RCS or falling back to SMS.

A quick network test is to open a normal website using only mobile data, then only Wi-Fi. If mobile data is disabled for Messages or the phone has no usable network, RCS may pause or fail. A data outage on one device can also force a fallback without anyone changing an app setting.

Why group chats are more fragile

Google says every participant in an RCS group must have RCS enabled for the conversation to use RCS features. One phone without supported service can force a different group messaging path. Add participants carefully, especially after someone changes phone number, switches iPhone to Android, or reinstalls an app.

Instead of deleting a large family group, create a temporary three-person test group with confirmed RCS users. Compare message behavior and check whether one person's number is saved twice in Contacts. Group threads can fork because the messaging identity and underlying protocol changed, not because the original history was erased.

After switching from iPhone to Android

An old iMessage registration can cause trouble if other iPhone users continue to send messages through Apple's service. Before switching, disable iMessage and FaceTime for the number on the old iPhone. Apple provides a deregistration process if you no longer have that device. Confirm your number is activated correctly on the Android phone, then enable RCS in the new default messaging app.

Do not assume changing an eSIM automatically updates every messaging registration. A successful call proves cellular service, but not necessarily that every chat service has transferred correctly. Ask one iPhone contact and one Android contact to send a new message rather than replying only inside old conversations.

Photos look blurry or arrive as links

A sharp photo arriving at low resolution may indicate MMS fallback, application compression, or a sender choosing a low-quality option. Apple's Messages troubleshooting includes photo-size settings, and carriers may impose size limits for MMS. Confirm the RCS status in the conversation before blaming the camera or cloud photo quality.

For a controlled test, send a moderate-sized image using RCS, then repeat over SMS/MMS where available. Compare the received dimensions and file size. If the problem is only in one chat, its participants and protocol are stronger suspects than the phone's gallery.

What about encryption?

Do not treat all green-bubble messages as having identical encryption. RCS security depends on the implementations, participants, messaging apps, and currently supported features. Apple has documented end-to-end encrypted RCS as a beta on supported carriers in newer software; it is not a reason to assume every cross-platform RCS conversation has end-to-end encryption today. For especially sensitive discussions, verify the security properties of the exact service you use.

Fix the failure in this order

1. Confirm both phones can send an ordinary message and use Internet data.
2. Check the carrier's RCS support for the iPhone and whether the iPhone's RCS setting appears.
3. Verify RCS status in Google Messages and that it is Android's default SMS app.
4. Test a new one-to-one conversation before testing an existing group.
5. Check whether someone recently changed devices, numbers, SIMs, or messaging apps.
6. Restart both phones and install official software/carrier updates.
7. Ask the carrier about registration failures before resetting network settings or deleting chat history.

If the new test chat works but an old group does not, preserve the old messages and create a fresh group only after checking participants. If neither new nor old conversations can activate RCS, capture the exact status text and escalate to the carrier or platform support. Resetting a phone is rarely justified by a messaging-protocol mismatch.

Official references

Apple — RCS support and encryption on iPhoneOfficial documentation checked 9 October 2026 Google — Troubleshoot RCS activationOfficial documentation checked 9 October 2026