Apple Explains How to Fix iMessage Not Delivered Alert in iOS 26

[MacRumors]

Apple today updated its iMessage troubleshooting support document to add a scenario that can occur in iOS 26. If you don't activate iMessage or an eSIM when setting up a new iPhone with iOS 26, it can prevent iMessage from working.

Apple says that iMessage does not activate automatically when setting up an eSIM in the Settings app after the initial iPhone setup period, so it needs to be done manually.

After activating an eSIM, users can open up the Settings app, tap on Apps, choose Messages, and then turn iMessage off and back on to get the feature to work as intended.

When iMessage is not properly activated after setting up an eSIM, users can receive a Not Delivered alert, have their messages sent as SMS/RCS messages in green bubbles, or see their iMessages delivered from an email address instead of a phone number.

Article Link: Apple Explains How to Fix iMessage Not Delivered Alert in iOS 26

 

[DBZmusicboy01]

They really need to fix the pile of Ultra Garbage that is iOS 26
The absolutely worst iOS of all time for MANY Reasons. It’s an abomination.

 

[Lizzard899]

Sounds like apple is just making excuses. They should just fix it on their own with a ios update and say its a bug. This sounds like too much to do those steps and them deflecting from them admitting its a ios bug ESIM should already be activated too when u backup from a prevous backup. Also if you go to settings apps then messages you should see if the check mark isnt by your phone under send and receive and its checked under your email then just click your phone number instead of clicking on or off just make sure send and recieve is checked off under your number

 

[turbineseaplane]

After activating an eSIM, users can open up the Settings app, tap on Apps, choose Messages, and then turn iMessage off and back on to get the feature to work as intended.

The old "unplug it and then plug it back in" routine 'eh?

Says a lot about Apple software quality these days.

 

[itsmemuffins]

What about the bug that started a few iOS’s ago where you don’t get a notification sound on your iPhone or Apple Watch when you get an iMessage?

 

[Nom4d]

What about the bug that started a few iOS’s ago where you don’t get a notification sound on your iPhone or Apple Watch when you get an iMessage?

I get sounds and notifications when i get an iMessage on my iPhone.

 

[BuffaloTF]

I just turned my phone off and back on again to resolve this same issue… I dunno.

 

[DEMinSoCAL]

What about the bug that started a few iOS’s ago where you don’t get a notification sound on your iPhone or Apple Watch when you get an iMessage?

That's me! Sometimes a haptic buzz on my watch, but rarely do I get an actual ding on my iPhone when a message comes in.

 

[DEMinSoCAL]

I get sounds and notifications when i get an iMessage on my iPhone.

A bug doesn't always affect everyone. iOS 26 has/had a WiFi bug that didn't affect me on my new iPhone 17 PM, but did affect enough people they put out a patch.

 

[Zwhaler]

How about fixing searching through my messages still being completely broken?

 

[HiVolt]

That's me! Sometimes a haptic buzz on my watch, but rarely do I get an actual ding on my iPhone when a message comes in.

That's been a bug that has come and gone for me for literally years now. Multiple watches, multiple phones.

 

[svish]

Good to know. Looks like an eSIM issue only and maybe Apple might change the settings in future iOS versions. Don’t see why iMessage cannot be activated automatically if eSIM is set up later.

 

[burratha]

I had a very similar linked issue recently when trying to set up an eSIM when I ported my mum's telco contract to a new provider. The new account had no spend cap set (banning extra costs like international calls) by default, so the phone was unable to send a text to the provider for iMessage to be able to register with the network. Although the phone and data worked fine, iMessage would not activate due to not being able to send the initial sms.

Once I added a small spend cap and allowed international calls, it immediately activated. weird.

 

[ThomasJL]

iMessage was working more reliably when it first came out on iOS 5 in 2011. In fact, while iOS has never been perfect, it was much more reliable and much less buggy back then. I wonder why that was? Oh right, it's because Scott Forstall was in charge of iOS at that time. And then that useless bean counting MBA degree holder Tim Cook fired Forstall in 2012. Cook kicked Forstall out and invited the bugs in.

 

[iMac The Knife]

iOS has been going downhill for years. It is really sad to me honestly, because it used to be so much better than Android. For the times they are a-changin'.

 

[iMac The Knife]

iMessage was working more reliably when it first came out on iOS 5 in 2011. In fact, while iOS has never been perfect, it was much more reliable and much less buggy back then. I wonder why that was? Oh right, it's because Scott Forstall was in charge of iOS at that time. And then that useless bean counting MBA degree holder Tim Cook fired Forstall in 2012. Cook kicked Forstall out and invited the bugs in.

This is what I've been saying for years now. iOS is still a great OS, but it has been going downhill for a while now. I don't know what the exact root cause is, but they need to fix it asap.

 

[tennisproha]

Sounds like apple is just making excuses. They should just fix it on their own with a ios update and say its a bug. This sounds like too much to do those steps and them deflecting from them admitting its a ios bug ESIM should already be activated too when u backup from a prevous backup. Also if you go to settings apps then messages you should see if the check mark isnt by your phone under send and receive and its checked under your email then just click your phone number instead of clicking on or off just make sure send and recieve is checked off under your number

Toggling imessage off and on is too many steps?

This bug has been around for years, it’s not new.

 

[Lizzard899]

Toggling imessage off and on is too many steps?

This bug has been around for years, it’s not new.

Again apple is making excuses on not admitting its a bug that they should fix. SO theyre making this workaround crap up. NO ITS APPLES ISSUE THEY NEED TO FIX IT NOT US