Not Getting Texts After Switching from iPhone to Android

Short answer

Your phone number is still registered with iMessage. When someone with an iPhone texts you, their phone sends it into Apple's service rather than as a normal text — and since you no longer have an Apple device receiving it, it goes nowhere. Deregistering the number fixes it. You can do that from the old iPhone if you still have it, or from a web page if you do not.

Why only iPhone friends’ messages vanish

The pattern is distinctive and it is the giveaway. Texts from Android friends arrive perfectly. Verification codes arrive. Your bank texts you. But messages from anyone with an iPhone either never show up or arrive days late in a batch.

Here is what is happening on their end. When an iPhone is about to text a number, it checks whether that number is registered with iMessage. If it is, the message goes over the internet to Apple’s service as an iMessage — blue bubble. If it is not, the phone sends it as a normal text.

Your number is still on that register. So their phone makes the wrong call, sends an iMessage, and Apple delivers it to the Apple devices associated with your number. You no longer have one. The message is not lost so much as delivered somewhere you cannot reach.

From your friend’s side, everything looks fine. The message shows as sent, often as delivered. They have no reason to think anything failed, which is why this can go on for weeks before anyone works it out.

Fix it from the old iPhone, if you still have it

This is the cleaner route and it takes a minute. Do it before you wipe or sell the phone.

Put the SIM back in the old iPhone, or at least make sure it is connected to Wi-Fi and signed in to the same Apple Account. Then:

  1. Open Settings and find the Messages section.
  2. Switch iMessage off.
  3. While you are there, switch FaceTime off too — it registers your number separately, and people trying to FaceTime you will hit the same dead end.

That is it. Turning the switch off tells Apple’s service to release the number. It is not instant — see the timing section below — but it is the most reliable version of this fix.

If you have already wiped the phone, this route is closed even if the phone is sitting in front of you. Use the web option instead.

Fix it without the old iPhone

Apple runs a page for exactly this, because the situation is common enough to need one. You enter your phone number, it sends you a confirmation code by text, you enter the code, and the number is deregistered.

Search for “deregister iMessage” and use the result on apple.com — we are deliberately not printing a URL here that we have not re-checked, because sending you to a stale link on a page about your phone number would be worse than making you search.

Two things to know before you start. You need to be able to receive a text at that number on your new Android phone, which you can — plain texts from the confirmation system arrive fine, since it is not an iPhone making the send decision. And if the code does not arrive within a few minutes, wait and try again rather than requesting it repeatedly.

Why it takes a few days to fully settle

The single most common follow-up is that someone deregisters, tests it immediately, and finds it still broken. This is expected.

Deregistering removes your number from Apple’s register. But every iPhone that has texted you recently has cached the fact that you were an iMessage user, and that cache does not clear the instant the register changes. Their phone keeps trying iMessage for a while before giving up and falling back.

Give it a few days. Most conversations sort themselves out within one to three, and the ones that do not usually involve someone who has not texted you in the interim — their cache is simply older.

What your friends can do to speed it up

If a specific person still cannot reach you after several days, there is a fix on their side, and it works per-conversation.

Ask them to open the conversation with you, delete the whole thread, and start a fresh one by composing a new message to your number. Deleting the thread clears the cached routing information along with it, so the new message triggers a fresh check — which will now correctly find that you are not on iMessage.

They should also check that the “send as SMS” setting is on in their Messages settings. That option makes an iPhone fall back to a normal text when an iMessage cannot be delivered. With it off, failed iMessages just sit there. It is on by default, but people turn it off to avoid text charges and then forget.

While you are at it: set up RCS

You have just fixed messages arriving. The next thing worth doing is making them arrive well.

Without RCS, every message between you and an iPhone friend is now MMS: compressed photos, no typing indicators, no read receipts, groups that barely function. With RCS, most of that comes back. It is a switch in your messaging app, and here is how to find it and what to do when it hangs.

This matters more than usual right after a number moves, because a recently ported line is exactly the situation where RCS registration is most likely to get stuck. If you switched carriers at the same time as switching phones, expect to do both fixes.

The lesson for next time

If you ever move away from an iPhone again, deregister before you hand the old phone over. It takes thirty seconds while the device is in your hand and saves a week of confusion afterwards.

The same applies in the other direction and people forget it just as often: before you get rid of an Android phone or move your number, turn RCS off. Registration lingering on a line you no longer use causes the mirror image of this problem. We wrote that one up separately.

Check your own setup

Once your number is out of iMessage, check what your conversations with iPhone friends will actually run on.

Run the checker

Version facts on this page: not verified yet — the site-wide verification pass has not been completed. See the update log

Related guides

Published 1 September 2026. Last reviewed 1 September 2026. This guide depends on facts F23, F28 in our verification table — if one of those changes, this page gets rewritten and the change is logged in the update log.