RCS read receipts between iPhone and Android users are a rollercoaster ride

When Apple announced its adoption of Rich Communication Services (RCS) for iMessage, Android users celebrated like they’d just won a free lifetime subscription to peace of mind. Finally, the messaging gap between Android and iPhone users seemed to be narrowing. Delivered statuses? Check. Typing indicators? Check. Read receipts? Well… not so fast.

Since iOS 18.1 rolled out, and particularly after the recent iOS 18.1.1 update, users on both sides of the smartphone aisle have reported some hilariously frustrating (and sometimes outright baffling) issues with RCS read receipts. From delayed messages to disappearing read statuses, it’s been a tech soap opera.

For iPhone users on iOS 18.1, many were delighted to see RCS capabilities, which brought texting with Android friends closer to the iMessage experience. But while messages sent through Google Messages showed up with delivery and typing indicators, read receipts often decided to take an extended vacation.

Some iPhone users found that read receipts were randomly turned off — not just globally but also for specific contacts. This discovery came after some awkward moments of, “Hey, why didn’t you respond?” and “Uh, I never saw you read it.” In some cases, it turned out these settings were accidentally toggled off. But the good thing is iOS allows per-contact customization for read receipts, meaning you may have to dig deep into your chat settings to fix this.

But that’s just one part of the puzzle. Even when read receipts are enabled, users report wildly inconsistent behavior. Messages sometimes arrive out of order. Others show as “Delivered” but never progress to “Read,” even if both parties swear they’ve enabled the feature. And in a particularly spicy twist, some Android users report not seeing read receipts from iPhones even when their iPhone buddies claim to have turned the feature on.

Android users aren’t getting off scot-free here. Many have experienced their own set of RCS quirks. Messages refuse to send, appear out of sequence, or — in the most ironic twist of all — fail to deliver the very read receipts they’re so desperate to see. One user noted that while they could see their son’s read receipts, their daughter’s RCS texts never showed as read. Same household, updated software, completely different outcomes. Is this a family drama or just bad luck? Well…

Another common complaint from Android users is that turning off their own read receipts doesn’t always stop their iPhone contacts from seeing when a message was read. While this might seem like a bug, it’s more of a “feature” (depending on your perspective) within the evolving RCS framework.

The underlying issue here seems to be that Apple and Google have approached RCS differently. While RCS is meant to unify messaging, its implementation still varies significantly between platforms. Apple’s iOS integrates RCS within iMessage, while Android relies on Google Messages. This disparity often creates an environment ripe for miscommunication — literally.

iOS updates, such as the jump to version 18.1.1, haven’t helped. And neither have multiple Google Messages app updates on Android. Instead of smoothing out the bumps, they’ve introduced new ones. Users report that read receipts work fine for a few days but then mysteriously stop. Is it a bug? A syncing issue? The jury’s still out.

If you’re caught in the RCS read receipt drama, here are a few steps to troubleshoot:

1. Check individual chat settings: On iPhones, open the chat, tap the contact’s info button, and confirm that read receipts are enabled for that person.

2. Toggle global settings: Both iOS and Android have system-wide settings for read receipts. Sometimes toggling them off and back on can work wonders.

3. Update your software: Always make sure your OS and messaging app are up to date. Newer updates might fix lingering bugs.

4. Reboot your device: It sounds cliché, but turning your phone off and on again can often resolve temporary glitches.

5. Communicate: If your read receipts aren’t working, let the other person know. They might need to adjust their settings, too.

The growing pains of RCS show that, while the protocol has potential, it’s far from perfect. Compatibility issues, inconsistent behavior, and a lack of transparency around settings have made the transition rocky for many users. Apple and Google’s differing approaches don’t help, and until both companies commit to ironing out these wrinkles, users will likely continue to face these bizarre messaging mishaps.

For now, the best advice is to be patient and keep an eye out for software updates. And maybe, just maybe, double-check those read receipt settings before accusing someone of ghosting you. RCS might be bringing us closer together, but it’s also making sure we never run out of things to complain about.