iMessage - put container(s) failed

HI,

IMTransferAgent is for sending with an AIM or Jabber account (there is s similar named one of iMessages) (or the LAN based Bonjour account)

Is it an AIM or Jabber Account that is involved ?

The size of the file look "wrong"

1) it says it contains 0 bytes

2) it still says it sent something (360kb)

3) do you really have a 2.5Tbps service ?

4) not surprising this took or is expected to take -52 secs (Minus 52 sec).

The App checks the Speed of the Internet connection it can see when it starts up. (it writes it to a .plist for the app)

If it is recording the "wrong" speed it will pay to restart the app.

9:37 pm Sunday; November 2, 2014

I have had this problem for months now. Same as above. Says the file is zero KB. I've tried with tons of different files (mostly small jpg, png etc) but it keeps saying "put container(s) failed". I't so annoying! And I can't receive files. Everything pops up OK in the iPhone but the mirror account on the computer shows nothing (well.. "Vendor request failed")

I have no AIM or Bonjour account active, just my iMessage...

SO annoying!

Hi,

The Messages app is one of the ones that is Sandboxed.

This tends to mean the app is set up in a way that a crash will not bring down other apps.

This is reality means that the app has a Read and Write path (~/Library/Containers/com.apple.iChat/Data/Library/Messages And then an Alias for a folder called Attachments), And a place where it actually stores the files that your are sent (~/Library/Messages/Attachments)

If, for some reason you have lost Read and Write permissions to any of the containing Folders then you will not be able to store the item being sent to you.

Use the Finder window.

Use the Go Menu whilst holding down the ALT key.

Select the Library that appears in the List.

Select CoverFlow view if you are not already.

From the Finder > View Menu > Show Path Bar (this shows icons of the folder across the bottom of the window).

From the View Menu > Show View Option choose the Modified column option.

Navigate to Messages/Attachments.

In the Path Bar right click the icon for the Messages folder and select Get Info.

Scroll to the bottom of the info panel.

Your Short name should appear.

Select this and Unlock the Padlock

Now use the little Cogwheel icon.

This should show that you Own the file by being greyed Out.

If required make it that you do Own it and also apply this to the Contents.

Repeat for all the folders in the other path involving the Contains folder.

It is long winded and time consuming but it is a less of a sledge hammer approach.

10:16 p.m. Wednesday; August 12, 2015

Thanks for the reply! I did what you described on both containers and messages folder but with no success. (I had the app closed and I even did a reboot) I also did a verify permissions/repair permissions in Disk Utility just for safety but still no success. :/

(I see that I am in the thread for Maverick although I have Yosemite, sorry for that)

Hi,

Repairing Permissions only looks at the System side of things and not your Personal setting in the ~/Library

In fact in the El Capitan beta the ability to Repair Permissions seems to disappear.

I would try this

Reset Home Folder permissions and ACLs Error

Scroll down to Linc's Green indicated answer and reset the Flags (Ownership and Permissions) on the Home folder.

He describes two methods of doing this.

It is more invasive than just looking like we did earlier as it checks all your files and changes them where required.

On the other hand it is more certain.

8:51 p.m. Thursday; August 13, 2015

Do you think this fix is valid in El Capitain also? I managed to update before I tried your fix. And I still got the same problem, though a little bit in another grammar. 😉

"There was an error sending the previous message. Would you like to try to send it again?"

Hi,

Yes.

In this case updating or even Upgrading to a newer OS X version is not going to touch your personal files.

7:15 pm Friday; April 22, 2016

I tried his step, and it looked like it worked (got to the step where the terminal showed $ before restarting), but it's still the same. If i try to send an image via message on my desktop to a cell, it says "Not delivered". And when people try sending me one I get the "There was an error trying to..."

So frustrating. I'm sure there's something I do wrong but I can't figure it out! 😟

Hummm.

This is odd.

In GoogleTalk chats and AIM chats I have issues with Pics in line in the chats and have to send them in folders or Zip them before sending (folders get zipped automatically).

I have no issue with sending pics to other Macs or iPhones with the iMessages account.

Try resetting the NVRAM How to Reset NVRAM on your Mac - Apple Support

8:24 pm Tuesday; April 26, 2016

Didn't work either. And I cant recieve images, even if I click the download-arrow. It lookes like this:

In the file transfer window, like this:

When I try to send, like this:

Frustrating as ****. :/

Hi,

DO you use a third party Firewall or a App like Little Snitch to monitor and allow which IP and Ports and App is using ?

http://alternativeto.net/software/little-snitch/ (This list is for all Platforms)

Little Snitch treats sub processes as separate items and can block the File Transfer items as they don't have "Messages" in the name.

IMRemoteURLConnection is for iMessages.

There is a similar named one but with File Transfer as part of the name that handles iMessages File transfer and a variation to that also handles AIMand Jabber File Transfers. They tend to show when a pic or file is sent.

8:53 pm Wednesday; April 27, 2016

YOU. ARE. A. GENIUS!

That was it! I'm so happy! Thank you thank you thank you!!!

R. Johns for President!

Hi,

Glad to help.

Thanks for letting us know.

8:26 pm Thursday; April 28, 2016