Message Send Failure: Every Cause, on iPhone and Android

Message Send Failure means the phone tried every way it has to deliver that message and none of them worked: iMessage or RCS over data first, then SMS or MMS over the cellular network. iOS marks the failure with a red exclamation point, Android with a red retry arrow, and the fix depends on which of those routes actually failed.

Most of the causes below have nothing to do with where you are, and clear in under a minute. One does not, and it is the reason this page exists: a phone connected to a data-only travel eSIM has no line that can send an SMS, so the fallback the message tries next was never going to work.

A message send is a short queue, not one attempt. The phone reaches for the richest channel available for that contact first, iMessage or RCS over data or Wi-Fi, and only opens SMS or MMS over the cellular network if that channel is unavailable or switched off. Apple's own troubleshooting page lists causes that have nothing to do with the network at all alongside the network ones: insufficient device storage, an address that is not quite right, and a device left on an operating system old enough that the newer protocols do not negotiate.

Android runs the same queue under a different name. Google Messages tries RCS first and SMS or MMS next, and Google's own troubleshooting guide adds a cause with no iPhone equivalent: a phone where Google Messages is not set as the default texting app can fail to send at all, independent of signal or plan.

Run through these before assuming the problem is travel, a plan or a network:

• It is not what being blocked looks like. A contact who has blocked you sees nothing unusual and you see the message as sent; Message Send Failure is closer to the opposite signal, that the phone could not even attempt delivery, so it points somewhere else entirely.
• The device is out of storage. A phone with no space left will not receive an incoming photo or video, and can fail on the send side too once its own message store cannot be written to.
• The operating system is out of date, which matters more for RCS than it used to: carriers periodically require a current version before they will negotiate the newer protocol at all.
• A group conversation you left, or one where a member switched to Android without deactivating iMessage first, both leave the group trying to reach a participant who is no longer reachable the way the thread expects.
• The message itself is the wrong size or type for the carrier, a long video sent as MMS being the classic case: some networks cap MMS well below what a modern phone will happily record.

These only appear once the phone is on a travel eSIM or roaming on the home line, and a page about the price of texting will not tell you which one applies:

• A data-only travel eSIM, with no phone number capable of sending or receiving SMS at all, so the fallback described in the note above has nowhere to go.
• The home line switched off entirely rather than merely limited, which is a common way to avoid charges while abroad. Switching a line off removes the SMS fallback along with the data, since neither can reach a line that is not active.
• A roaming agreement that does not carry RCS even where it carries voice and SMS normally. RCS on iPhone needs iOS 18 and a carrier that supports it, on the home network and on whichever network the phone has roamed onto, so a trip that worked over RCS last year can fall back to plain SMS this year on a different partner network with nothing on the phone having changed.
• No Wi-Fi Calling turned on, on a line with a weak cellular signal. It is the setting that lets SMS travel over Wi-Fi when the cellular signal will not carry it, and a line that has never had it enabled cannot use that fallback either.

In the order that clears the most cases fastest:

1. 1Tap the failed message, choose Try Again, and if it fails again choose Send as Text Message, unless the line is data-only, in which case skip straight to step four.
2. 2Toggle airplane mode on and off. It forces the phone to reselect a network and clears a surprising share of one-off failures on both platforms.
3. 3Check which line the message tried to send from (Settings, Apps, Messages, Send and Receive on iPhone) and confirm that line has signal and, for SMS, is not the one you switched off for the trip.
4. 4If the line is data-only, turn off Send as Text Message so the phone stops trying a fallback that cannot work, confirm data is connected, and send the same message again as an iMessage or RCS chat.
5. 5Update the operating system if it is behind, and check storage if the failure is on receiving a photo or video rather than on sending text.
6. 6On Android, confirm Google Messages is the default app and RCS chats are turned on for that number, which is the first check in Google's guide.

None of this is a reason to avoid a data-only eSIM. Most travel messaging happens over iMessage, RCS or an app like WhatsApp, and none of those need a phone number once they are set up. It is a reason to know, before you leave, whether the travel line you are buying can send SMS if you need it to: some providers sell a number capable of calls and texts alongside the data, most do not, and the difference sits in the plan details rather than in the headline price.

Check that before you buy rather than after a message fails to explain why. Compare eSIM plans for your destination and read what each one actually includes beyond the gigabytes.