Google Messages is having trouble sending media files over RCS (Update: Fix)

The issue surfaced in the latest version of Google Messages, where the app’s RCS implementation failed to transmit images, videos, or audio clips to fellow Android users. Instead of falling back to SMS/MMS, the messages stalled, leaving senders with error prompts and recipients without any notification. Because Google positions Messages as the flagship RCS client for the Android ecosystem, the malfunction directly undermined its promise of iMessage‑style seamless media sharing and raised concerns about the reliability of Google’s universal RCS rollout.

RCS has been a cornerstone of Google’s strategy to standardize richer messaging across carriers, handset makers, and the Play Store. The feature competes with entrenched cross‑platform apps such as WhatsApp, Signal, and iMessage, which already deliver reliable media exchange. A visible outage in Google’s own flagship messaging app not only stalls user adoption of RCS but also gives rival services a persuasive argument that they remain the safer choice for everyday communication. The glitch also highlights the fragility of a carrier‑dependent protocol that still relies on heterogeneous network implementations worldwide.

Google’s swift deployment of a fix within days demonstrates its commitment to maintaining RCS credibility, but the episode underscores the need for more rigorous testing before pushing updates that affect core messaging functions. Observers should monitor whether the patch fully restores media delivery across all carrier networks and Android versions, and whether Google introduces additional telemetry to catch similar regressions earlier. The incident may also prompt carriers to re‑evaluate their support for RCS, potentially accelerating discussions around a more cloud‑centric messaging layer that bypasses carrier variability.