If you rely on Google Messages for work or personal chats, you may have run into a frustrating wall. Users across Reddit are reporting that when Rich Communication Services is enabled, media files simply will not send to other Android phones. GIFs, pictures, photomoji, and stickers all fail to arrive, leaving senders confused and recipients waiting.
The issue appears limited to Android-to-Android transfers. Sending the same media to an iPhone with RCS enabled works without problems, according to multiple reports. Switching back to SMS/MMS resolves the issue for most affected users, though that means losing the benefits of RCS entirely.
What's Going Wrong
Reports from Reddit threads describe a consistent pattern. With RCS turned on in Google Messages, media uploads fail silently or show a sending indicator that never completes. The files never reach the recipient. The problem spans different Android manufacturers and Android versions, suggesting this is an app-level issue rather than a device-specific bug.
A wave of complaints appeared on Reddit over the past few weeks, with users documenting the problem across multiple discussion threads. The issue seems to have emerged alongside recent Google Messages updates, though Google has not confirmed any connection. Third-party monitoring services tracking Google app stability have not flagged widespread outages, which suggests this may affect a subset of users rather than the entire RCS network.
Why This Matters for Your Workflow
For professionals using Android devices in collaborative environments, this bug creates real friction. Teams sharing screenshots, design mockups, or recorded walkthroughs through Google Messages hit a wall without clear explanation. The workaround of switching to SMS/MMS restores functionality but sacrifices the higher resolution, read receipts, and typing indicators that RCS provides.
Agile teams often use messaging apps as informal channels for quick feedback during sprints. When media sharing breaks down, that informal communication channel becomes unreliable. You might find yourself reverting to email or scheduled meetings for things that used to be a quick screenshot sent over chat.
Say you are a product owner reviewing wireframes with your development team. Someone sends you a new mockup via Google Messages and it never arrives. Without knowing about this bug, you might assume the designer forgot to send it, leading to unnecessary back-and-forth. Awareness of the issue lets you advise your team to use Google Drive links or email as a backup until Google addresses the problem.
The asymmetry is also worth noting. Since media reaches iPhones without issues, cross-platform teams may not experience the problem at all. This could lead to confusion when only some team members report missing files.
Who Should Watch This
Android users on any carrier who depend on RCS for daily communication should monitor this situation. Pixel users may see faster updates through the Google Play Store, while Samsung and other manufacturer users depend on carrier-approved app versions. If you manage a mixed-device team, consider establishing a fallback protocol for critical media sharing.
Troubleshooting Attempts
Users have tried a variety of fixes without success. Rebooting the device, clearing the app cache, force-stopping Google Messages, and resetting network settings all left the problem intact. Toggling the RCS connection on and off also proved ineffective. One workaround involves clearing the app's storage data, though this also erases saved Photomoji and removes the ability to create new ones. Until an official fix arrives, switching to SMS/MMS remains the most reliable temporary solution, despite its limitations.
What to Watch Next
Google has not issued a public statement about the bug. Pay attention to Google Messages update notes in the Play Store, as fixes for RCS issues typically arrive through incremental app updates. You can also enable automatic updates to ensure you get patched versions as soon as they roll out. If your team depends heavily on RCS media sharing, document any patterns you notice, such as whether certain contacts consistently fail to receive files or whether the problem correlates with specific Android versions.
Bottom line: If you depend on RCS media sharing between Android devices, keep SMS/MMS as a fallback until this gets patched.
Key takeaways
- RCS-enabled Google Messages is dropping media files sent to other Android phones
- SMS/MMS switching restores functionality but loses RCS features
- Standard fixes like cache clearing and restarts have not worked for most users
- The problem does not affect media sent to iPhones on RCS
- No official fix or timeline has been announced
Frequently asked questions
Can I still send media to iPhones using Google Messages with RCS?
Yes, according to user reports, media transfers to RCS-enabled iPhones work without issues.
Does switching to SMS/MMS affect my message history?
No, your conversation history remains intact, but you lose RCS features like typing indicators and high-resolution media sharing.
Will my photomoji be deleted if I clear storage to fix this?
Possibly. One user reported losing their Photomoji tab after clearing storage, so consider this a last resort.
Is Google aware of this issue?
Multiple outlets have reported the issue, and at least one has sought comment from Google, but no official response or timeline for a fix has been announced.
Does this affect all Android phones equally?
Reports suggest the problem spans multiple manufacturers and Android versions, though the exact distribution of affected users is unknown.
Inspired by reporting from: androidauthority.com