imessage gives error "not delivered," even when sending to an iPhone and the message does get delivered

I keep getting a "not delivered" error message with the red exclamation point when I use iMessage on my MacBook, texting to iPhone users. But when I look at the conversation on my phone, the messages show up in blue. And recipients respond, so the messages are clearly going through. Why am I getting the errror? It's confusing, because I can't tell if a message gets delivered for sure.


Both my MacBook and my iPhone (7) are updated with the latest OS and iOS. I think this problem started after the latest updates, in fact.

MacBook Pro, iOS 11.2.1

Posted on Jan 7, 2018 6:21 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 1, 2018 3:13 PM

I was having the same issue - I had Messages set up on 2 phones, 2 computers and an iPad. Only the computer with High Sierra had the issue. It is only an issue with iMessage, not SMS/MMS. Messages were being send and received, but the error flag was still occurring.


The issue was resolved as soon as I logged out of the account on an older machine that could not be updated with High Sierra.


I did this through the Preferences/Accounts menu of Messages on the older machine. First I unchecked 'Enable this account,' then I signed out.


On the iPhone in Settings/Messages under 'Text Message Forwarding,' I had two MBP's listed. Logging out of Messages on the older unit removed the listing for the second machine in this menu.


Perhaps try either logging out of additional machines that aren't on the latest build or with the 'Text Message Forwarding' option try to disallow other devices from sending.


// www.ROCKandREVIEW.com

84 replies
Question marked as Top-ranking reply

Aug 1, 2018 3:13 PM in response to wvillagealex

I was having the same issue - I had Messages set up on 2 phones, 2 computers and an iPad. Only the computer with High Sierra had the issue. It is only an issue with iMessage, not SMS/MMS. Messages were being send and received, but the error flag was still occurring.


The issue was resolved as soon as I logged out of the account on an older machine that could not be updated with High Sierra.


I did this through the Preferences/Accounts menu of Messages on the older machine. First I unchecked 'Enable this account,' then I signed out.


On the iPhone in Settings/Messages under 'Text Message Forwarding,' I had two MBP's listed. Logging out of Messages on the older unit removed the listing for the second machine in this menu.


Perhaps try either logging out of additional machines that aren't on the latest build or with the 'Text Message Forwarding' option try to disallow other devices from sending.


// www.ROCKandREVIEW.com

May 16, 2018 4:21 AM in response to quaintproductions

I also suggest...one by one (as will take ages to change all to +44) when you use imessage for a particular person that comes through as an imessage, update the contact on the mac. Click ADD to existing contact, find contact, then delete the number with the "0" at the beginning, and keep the +44 version, then save. That should also update your phone instantly (if you have it connected/synced right). Let me know if this works out for you.

Jan 17, 2018 12:48 PM in response to mesh-arc

Hi,


There is a long term issue with Messages and the iMessages account that has been present since version 7.0.1 at the OS X 10.8.2 update.


This is when Apple started using the Serial Number to make the login Device Specific.

AT that time most people with issues had missing Serial Number where it had not been "flashed" back to repaired (replaced) Logic/Mother boards.


There were 2 version 8s of Messages.

These continue until we get to version 11 in High Sierra (MacOS 10.13.x)


At each update and Upgrade a few (and the number is small compared to the numbers using any particular Mac OS) who seem to have this issue.


People notice that iMessages are not syncing properly but as most use both iPhone number and Apple IDs as contact IDs the issue can be hidden.


Testing is the only way to check.


It was this phrase that made me think you were using SMS as well as iMessage


... when I use iMessage on my MacBook, texting to iPhone users. ...

If the Mac is not logged into the iMessages server it may still send SMS if linked to the iPhone to do so.

Obviously in some cases the phone might not be able to send SMS and convert it to iMessages instead.


If testing proves it is the account is not logged in then you are most likely going to need Users Tip

When the iMessages account will not Login


The last bit in that Users Tip is about phoning Apple Support (Apple Care)
Apple ID issues are free to fix. However you need to move up the chain of responders until you get someone who can check the server.

They should be able to tell you if the server is blocking your Apple ID when used by your Mac (It is Device Specific).

More recently the responders have been asking for data grabs and other log details in an effort to find out why it happens. (I have not spotted a trend for OS Version or Mac Model or particular ID types such as @me.com or @mac.com or even @icloud.com or non Apple issued emails as Apple ID)


It is no good doing a Reinstall if suggested until you know if the server is blocking the ID as if it is it will still be blocked after the Reinstall.






User uploaded file

8:48 pm Wednesday; January 17, 2018


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone 6 iOS 11.x and an iPad (2)

Sep 4, 2018 12:55 PM in response to OrgSync

This appears to have worked for me as well. Thank you!!


To save people from having to search on "PRAM" - here are the steps to reset it:

  1. Shut down the computer.
  2. Press the power button.
  3. Before the grey screen appears, press the Command, Option, P, and R keys at the same time.
  4. Hold the keys until your computer restarts and you hear the startup sound a second time.
  5. Release the keys.

Sep 12, 2018 2:27 PM in response to wvillagealex

Deleting /Library/Messages worked for me for at least a few minutes (it consistently happened with one particular person). This is the easiest way to do it:


  1. Quit Messages
  2. Open Terminal
  3. Move the Messages folder to a backup location:
    sudo mv /Library/Messages /tmp/
  4. Open Messages


If for some reason this breaks Messages, do the following:


  1. Quit Messages
  2. Open Terminal
  3. Move the new Messages folder out of the way: sudo mv /Library/Messages /tmp/Messages.2
  4. Move the old Messages folder back: sudo mv /tmp/Messages /Library/Messages
  5. Open Messages


Based on macos - Messages on Mac displaying "Not Delivered" but message is being delivered - Ask Different.

May 16, 2018 4:15 AM in response to wvillagealex

Right, as far as I can see it's to do with iMessage (on Mac) not doing great with how it reads the mobile number. For example, I can 99% guess, that if you wrote +44 then the mobile number (minus the 0 from the front of course) when you send in iMessage on a Mac (change +44 to match your country code of course) it will then work as it should. I came across this when I accidentally re scyned and duplicated my contacts once.. any way.. annoying I know, but add +44.

Aug 2, 2018 8:22 AM in response to wvillagealex

I found that certain characters cause the error. As noted, the messages do send, but give a 'not delivered' message on the Mac. The comma [yes, the lowly comma] is one. Here's an example from when I was sending a text to a friend about and A/C:

User uploaded file

Same text. With the COMMA, it gives the error. I've confirmed this many times now.


A clear, and reproducible BUG!

Jul 27, 2018 12:33 AM in response to JordanPeele

Right,

but to re-iterate; the issue that has crept up with message in the cloud and the recent updates is that messages will SAY they are not delivered, while they are, in fact, immediately and consistently delivered.

If you are quick, you can sometimes see the 'read' (if the receiving devices has that enabled). just to switch to the red exclamation mark / not delivered a split second later. Sometimes they will even update and no longer be 'red' (without having re-tried it.

There is something going on since message iCloud was enabled.

Jul 27, 2018 12:55 AM in response to kaley254

Right,

but to re-iterate; the issue that has crept up with message in the cloud and the recent updates is that messages will SAY they are not delivered, while they are, in fact, immediately and consistently delivered.

If you are quick, you can sometimes see the 'read' (if the receiving devices has that enabled). just to switch to the red exclamation mark / not delivered a split second later. Sometimes they will even update and no longer be 'red' (without hav

There is something going on since message iCloud was enabled.

Jul 18, 2018 11:52 AM in response to Rosebudster

Hi,


Having now read several threads on this new issue it seems it is a server issue related to the fact that iCloud can be used to sync iMessages across devices.


At the moment an obvious fix has not come to light.



User uploaded file

7:52 pm Wednesday; July 18, 2018


 iMac 2.5Ghz i5 2011 (Sierra)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 MacBookPro 15" 2016 (High Sierra 10.13.x)
 Mac OS X (10.6.8),
 iPhone 6 iOS 11.x and an iPad (2)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

imessage gives error "not delivered," even when sending to an iPhone and the message does get delivered

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.