iMessages won't send pictures after high sierra update

I recently updated a number of my Macs to High Sierra. One of them now won't successfully send pictures via iMessage to an iPhone. I have tried multiple iPhones with the same result. The iPhone user sees a "downloading" icon like the one pictures below, but never receives actual image. The iPhone has the latest iOS. Any suggestions?User uploaded file

MacBook Air (13-INCH, MID 2011)

Posted on Oct 17, 2017 6:57 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 3, 2018 9:55 PM

After spending over 5 hours with Apple Support and literally reinstalled everything over, we narrowed it down to a corrupt database within the Library Preferences. So the fix that worked for me was:


1. From your desktop, hold down "Option" and click the Go tab.

2. Scroll down to Library

3. Go down to the Messages folder

4. Take all of the files ending with .db and pull them out of the folder onto the desktop.

5. Restart computer and see if it works. Your messages should generate new files and if it does work, you can trash the old .db files.

22 replies
Question marked as Top-ranking reply

Jan 3, 2018 9:55 PM in response to bshipp

After spending over 5 hours with Apple Support and literally reinstalled everything over, we narrowed it down to a corrupt database within the Library Preferences. So the fix that worked for me was:


1. From your desktop, hold down "Option" and click the Go tab.

2. Scroll down to Library

3. Go down to the Messages folder

4. Take all of the files ending with .db and pull them out of the folder onto the desktop.

5. Restart computer and see if it works. Your messages should generate new files and if it does work, you can trash the old .db files.

Jan 7, 2018 12:22 PM in response to Antonio Sarmiento Cárdenes

Hi,


The missing Code Signature is an OS install issue rather than a server issue.


Also although we were "promised" iCloud integration Messages and the iMessages Account is yet to be an iCloud app.


I have tried Little Snitch version 4 in High Sierra and my version for the File Transfer process has a Code Signature.

So does the IMRemoteURLConnectionAgent that handles the Login process.


It seems a process will run without a Code Signature.

It also seems possible though that there checks to make sure you are logged in properly which then may effect other processes governed by the same app.


From the picture above my Brother Printer works.

From evan.v's picture, further above, it seems his IMRemoteURLConnectionAgent does not have a Code Signature but he appears to be logged in but still cannot send pictures.


The Code Signatures appear to be in the folders where the executable file is.

Some Hard drive Name/System/Library/Frameworks folders have Code Signature files in based on the process name.


In Hard drive Name/System/Library/Messages/Plugins there are three Plugins one of which is for iMessage

Deeper in this folder is a Code Signature for that process.


It would take a very long time to find each and every process and find if they have Code Signatures and even if they are working properly.


From what I can see a Reinstall might be the only option at the moment.






User uploaded file

8:19 pm Sunday; January 7, 2018


 iMac 2.5Ghz i5 2011 (El Capitan)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 iPhone and an iPad (2)

Jan 3, 2018 1:05 PM in response to bshipp

I can not send messages at all after updating to High Sierra. But only a few Macs are effected, on some it still works as expected.


What I tried:

- logout / login to messages
- reset NVRAM

- turn off Little Snitch

- add "allow all" rules for "IMRemoteURLTransferAgent", "IMRemoteURLConnectionAgent"


Nothing helped.


But by adding rules for IMRemoteURLTransferAgent I figured out: The code signature is marked as invalid, only on the Macs which can't send messages.


Any ideas how to solve the code signature error?

Jan 3, 2018 1:38 PM in response to evan.v

Humm,


My Little Snitch version 3.8.2 shows me this:-

User uploaded file

Yours looks like a newer version than mine.

Mine does list all the IP addresses it can use for that process. They are all Apple ones.


Your pic is also of the Login process for iMessages and not the Transfer one.


I see just one IP for File Transfers.

User uploaded file


Does the red icon link to a way of resolving the Code Error ?





User uploaded file

9:38 pm Wednesday; January 3, 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)

Jan 3, 2018 1:45 PM in response to Ralph-Johns-UK

The IMTransferAgent does not have a invalid code signature, only IMRemoteURLConnectionAgent.


The red icon does not link to solve it, it's just an indicator.


Out of 4 MacbookPro 2 can not send messages. All 4 have a valid code signature for "IMTransferAgent", but those who can not send have the invalid code signature for "IMRemoteURLConnectionAgent". That's the only difference I could find so far. (Same OS version, same Little Snitch version)

Jan 4, 2018 12:18 PM in response to evan.v

Hi,


Version 4 but with Sierra at present:-

User uploaded file


Still working through other items to get a more detailed state of play as it were.


This about IMTransferAgent

User uploaded file


Will try version 4 of Little Snitch on High Sierra.



User uploaded file

8:18 pm Thursday; January 4, 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)

Jan 6, 2018 2:10 PM in response to Ralph-Johns-UK

Hi. I'm experiencing the same issue. I have notice that several iCloud services fails to sync or to allow options like sending pictures every while even with all services with the status in green. iCloud and Messages are really a mess. Instead of focusing in many features that nobody needs, they should try to make the current apps and services to run correctly.

Oct 31, 2017 1:31 PM in response to devmodenull

Hi,


It can be Little Snitch if this process is not allowed:-

User uploaded file

This tends to pop up if there is a sync around where you have sent something from an iPhone or another device.


Not to be confused with:-

User uploaded file

IMRemoteURLConnectionAgent is the process for Logging the account into the iMessages server.


IMRemoteURLTransferAgent is the actual one for the allowing of sending pictures and files and also seems to be the name of the process in older versions


It can be a block or not allowed in Little Snitch or other Firewall apps.

It can also be down to the DNS servers listed not finding the server.







User uploaded file

8:31 pm Tuesday; October 31, 2017


 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)

Nov 8, 2017 6:57 PM in response to bshipp

An update as posted here Re: iMessage (Stuck Downloading images):


After days of trial and error, I was able to solve this problem by doing two main things: 1. completely resetting imessage, and 2. resetting NVRAM.


Step 1: Resetting imessage: I logged out and completely exited the application. Then, I followed the instructions here and improvised further by clearing the entire folder ~/Library/Messages: WARNING: you will lose all your chat history/attachments/etc. Restart your computer and go straight to step 2.


Step 2: Resetting NVRAM: see here How to reset NVRAM on your Mac - Apple Support


I also did a hard reset on the iPhone.


Don't open messages until these steps are done.


Give this a shot and see if it helps you.

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.

iMessages won't send pictures after high sierra update

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