If you keep seeing “Message Blocking Is Active” when a text won’t send, the problem usually isn’t some mysterious phone failure. Most of the time, it comes down to one of a few practical causes: a carrier-side messaging block, a blocked contact, a misconfigured iPhone or Android messaging setting, or a network/account issue. The fix depends on whether the problem happens with one person, all contacts, or only certain message types like SMS, MMS, or RCS.
Quick answer: To fix “Message Blocking Is Active,” first check whether the issue affects one contact or everyone, confirm your signal and mobile line are active, verify the number is correct, make sure neither side has the number blocked, then review your messaging settings. On iPhone, check Settings > Apps > Messages, turn iMessage off and back on, and enable Send as Text Message. On Android, make sure Google Messages is the default SMS app, confirm RCS/SMS support, and check your carrier account for message blocking or plan restrictions.
What “Message Blocking Is Active” actually means
This message usually means your phone or carrier is stopping the text before delivery. T-Mobile’s own support documentation says a “Message blocking active” error for a text to a specific person can mean that their message blocking is active, and its broader message-blocking page confirms that carriers can block outgoing and incoming SMS and MMS at the account level. That’s why this error can look like a phone problem even when the real cause lives in the carrier account or line settings.
On iPhone, it’s also worth noting that iMessage problems and SMS/MMS problems aren’t the same thing. Apple’s current support pages explain that blue bubbles are iMessage, while green bubbles are RCS, SMS, or MMS. If iMessage is unavailable and your phone isn’t set to fall back correctly, a message can fail even though the person’s number itself is fine. Apple’s green bubble guide and Apple’s Messages troubleshooting both reflect that distinction.
Why this happens
1. The number or contact is blocked
If the problem happens with one specific person, start here. Carrier guidance and Apple guidance both point to blocked contacts as a common reason texts don’t go through. That doesn’t automatically mean the other person blocked you; it may simply mean you blocked them or the number was filtered into a spam/block list by mistake. If you want a deeper breakdown of the signs, my guide on blocked on iMessage signs covers the difference between actual blocking clues and normal delivery failures.
2. Your carrier account has message blocking enabled
This is the most literal cause behind the exact error text. Some carriers let the account owner turn messaging blocks on or off for the line, and those controls can affect text and picture messages. If that setting was enabled intentionally, by parental controls, by an account manager, or through plan-level restrictions, your phone can look normal while the carrier silently rejects the message. T-Mobile’s message blocking page is one of the clearer current examples of this.
3. iPhone settings are wrong after a SIM change, new device setup, or activation issue
Apple says message problems after setting up a new device can show up as green bubbles, split threads, or failed sending. Its current guidance is to verify the active line, confirm the correct number under Send & Receive, and turn iMessage off and back on. If your iPhone recently changed SIMs, eSIMs, or devices, this is one of the first places to check.
4. Android isn’t using the right default texting app or RCS is misbehaving
Google’s official troubleshooting says Google Messages should be set as the default texting app, the SIM must be inserted properly, the carrier must support the message type, and RCS availability varies by carrier. If you switched messaging apps, moved from iPhone to Android, or recently enabled/disabled chat features, that transition alone can break sending until the default app or RCS state is corrected. Google’s message fix guide and Google’s RCS settings guide both call this out.
5. Your plan, credit, signal, or mobile data is the real problem
Google explicitly tells Android users to check carrier support, account balance or credit, signal, airplane mode, and mobile connectivity. Carrier support pages also point to low balance, bad signal, full storage, and outdated software as real messaging blockers. In other words, “Message Blocking Is Active” can be the visible symptom even when the deeper issue is that your line can’t currently send the message type you’re trying to use.
A fast way to identify the real cause
| What you see | Most likely cause | Best next step |
|---|---|---|
| Only one person fails | Blocked contact, wrong number, or their line has message blocking | Check the contact, retype the number, ask them to verify blocking on their side |
| Everyone fails | Carrier issue, plan issue, SIM problem, or messaging settings problem | Check signal, line status, account balance, messaging app settings |
| iPhone shows green bubbles or Not Delivered | iMessage unavailable or SMS fallback not working | Turn iMessage off/on, enable Send as Text Message, confirm active line |
| Android can send in one app but not another | Wrong default SMS app or RCS/chat conflict | Set the correct default SMS app and review RCS settings |
| Pictures fail but plain texts work | MMS/data/APN issue | Check mobile data, MMS settings, and APN reset if needed |
How to fix “Message Blocking Is Active” step by step
- Figure out whether it’s one contact or all contacts. This is the fastest split in the whole troubleshooting process. If one number fails, think contact block, wrong number, country code, or recipient-side restrictions. If all numbers fail, think line, carrier, SIM, or app settings.
- Check signal, airplane mode, and mobile line status. Make sure airplane mode is off, signal is present, and your SIM or eSIM line is active. Apple specifically tells iPhone users with new-device message issues to verify the selected mobile line, while Google tells Android users to check signal and SIM status.
- Verify the number exactly as entered. Re-enter the contact manually, especially if this happens with an international number or a recently saved contact. Carrier documentation specifically mentions checking the number and country code, which sounds basic but solves more cases than most people expect.
- Check whether the contact is blocked on your phone. On iPhone, review blocked contacts in the current Apple path under Privacy & Security. On Android, look in your Messages app’s blocked numbers or spam settings. If you’re already troubleshooting other Android account or app-state problems, the same clean-reset approach I used in my Google account sign-in fix often applies here too: start with the least disruptive checks first, then move deeper only if needed.
- On iPhone, reset the Messages basics. Go to
Settings > Apps > Messages. Turn iMessage off, wait a few seconds, and turn it back on. Then openSend & Receiveand confirm the correct phone number is selected. Also enable Send as Text Message so the iPhone can fall back when iMessage is unavailable. If you see a red exclamation mark, tap it and try again or send as text. - On Android, confirm the right messaging stack is active. Make sure Google Messages or your preferred SMS app is the default SMS app, then review
Messages settings > RCS chats. If RCS is stuck, unsupported by your carrier, or acting inconsistently, disable it temporarily and retry with standard SMS/MMS. Google documents both the default-app requirement and the carrier-support limitation. - Restart the phone and update the app/software. This isn’t glamorous, but it matters. Apple, Google, and carriers all include software updates and device restarts in their current messaging troubleshooting flow because stale app state and interrupted service registration are common causes.
- Reset network settings if the phone recently changed carriers, SIMs, or devices. AT&T and T-Mobile both include network-reset guidance in their messaging support, and Apple’s own guidance strongly points users toward line and activation checks after setup changes. This is especially relevant if mobile data itself is flaky, calls are acting strangely, or the issue started right after migrating phones.
- Check account balance, plan restrictions, and carrier-side blocking. Prepaid balances, parental controls, account-level blocks, and short-code restrictions can all interfere with sending. If you’re on a family or business plan, another account owner may control the blocking options. T-Mobile’s documentation is explicit that primary account holders can manage message blocking from the account side.
- Ask the other person one direct question. If only one conversation fails, ask them whether they have your number blocked, recently changed carriers, moved from iPhone to Android, or enabled any message filtering on their line. This avoids hours of guesswork. If you’re trying to tell the difference between a technical failure and a social block, my iMessage blocking guide explains which signs are meaningful and which ones aren’t.
iPhone-specific fixes that solve this most often
On iPhone, the most effective fixes are usually clustered around the Messages settings Apple now exposes under Settings > Apps > Messages. In practice, the sequence that works most often is:
- Confirm the correct phone line is active
- Turn iMessage off and back on
- Check
Send & Receivefor the correct number - Enable Send as Text Message
- Retry the message from the red exclamation mark if available
- Reset network settings if the issue started after migration or carrier changes
If the thread suddenly switched from blue to green, don’t assume the other person blocked you. Apple’s own guidance says green bubbles can also mean iMessage is off, unavailable, or that the conversation is using SMS/MMS or RCS instead.
If your iPhone has been behaving oddly across other apps after updates or account changes, it’s also worth looking at how other cached-state issues behave on Apple devices. My article on clearing cookies on iPad is about browsers rather than Messages, but it shows the same wider troubleshooting principle: clear stuck state before assuming hardware failure.
Android-specific fixes that solve this most often
On Android, the biggest mistake is treating all message failures as the same thing. Google separates SMS/MMS support, RCS support, default app selection, SIM state, and carrier support. If one of those pieces is out of place, you can send in one situation and fail in another.
- Make Google Messages the default SMS app
- Check whether RCS chats are connected, unsupported, or stuck verifying
- Turn RCS off temporarily and test standard SMS
- Confirm mobile data works if MMS is failing
- Check that the SIM is seated properly
- Verify plan balance or credit on prepaid service
- Update the Messages app and Android system software
If Android app state looks corrupted more broadly, follow a clean escalation path instead of random toggling. The sequence I used in my Android package error guide is a good model here too: verify the simplest settings first, then move into cache clearing, app resets, and system-level checks only when the obvious fixes don’t stick.
What not to assume
The most common wrong conclusion is: “This error proves the other person blocked me.” It doesn’t. Apple doesn’t expose a clean blocked-you notification to the sender, and carrier message blocking, line problems, wrong numbers, green-bubble fallbacks, and default-app issues can all create almost the same user experience. A real diagnosis comes from the pattern, not from one failed attempt.
When you should contact your carrier
Contact your carrier if any of these are true:
- You can’t send texts to anyone
- The error started right after a plan, SIM, or number change
- You’re on prepaid and balance-sensitive service
- The account owner may have enabled message blocking
- Short codes or verification texts are failing across multiple services
- You already checked blocked contacts, iMessage/RCS settings, and network basics
At that point, ask them specifically to check for SMS/MMS blocks, short-code restrictions, line provisioning issues, and account-level message blocking. Being precise with the carrier saves time because “texts don’t work” is much broader than “please check whether outbound SMS blocking is enabled on my line.”
Final Thoughts
Message not sending and the “Message Blocking Is Active” error usually come back to one of four things: blocking, settings, carrier restrictions, or line connectivity. The fastest fix is to stop guessing and narrow the scope first: one contact or everyone, iPhone or Android, SMS or RCS/iMessage, plain text or picture message. Once you do that, the right fix usually becomes obvious. Start with the quick checks, move through the device-specific steps, and if the error still stays put, have your carrier verify that your line isn’t blocked at the account level.
