Yahoo file transfers fail

Have you tried TroubleshootingTips as it outlined in ReportingBugs? Does this occur with only one buddy or all that you've tried to send files to? Does this occur on every network - if you have the ability to try another internet connection, please give it a shot :)

I have to second this. Tried on 2 MacBook 1 was extremely new so everything is clean without any plugins whatsoever.

r_yapeter... the same questions apply to everyone who is encountering this problem. I unfortunately have no yahoo contacts to try this with, so we need you guys to be able to do some legwork to help narrow the problem down. So again:

1. Does this occur with many buddies or just one or two?
2. Does it occur on every network, or do certain network configurations make a difference?
3. If this only occurs with certain buddies, are they using a specific Yahoo client in common?

I have read recent threads in the PC yahoo messenger forums suggesting that file tranfer in general has been acting up the last few days. it is possibly a yahoo server thing. my understanding of yahoo file tranfer is even the newer p2p version of it (vs the old http requests version), STILL requires negotiation between peers by yahoo's middle man server, if that's a no go, file tranfer is a no go..But It'd be worth looking into.

This always happens with one of my buddies. The transfer starts instantly, way before he gets any request for transfer. This is not a recent thing either. I do not have any extras installed in Adium either. My friend uses 8.1.0.249 Yahoo messenger.

Also MyYahoo Module (8.0.0.1)

We currently only support yahoo transfers of about a megabyte due to a libpurple limitation.

I'm transferring images that are well under a megabyte (200-500kb usually) and they're behaving exactly as described here. Adium immediately sends the data "somewhere", but my contact never sees a thing. Tested with a fresh install of Adium 1.2.4 on Leopard communicating with a fresh install of Yahoo messenger 8 on WinXP.

I used to be able sometimes to transfer files to my Yahoo contacts, but more importantly -- this used to always work from my Adium to another Adium.

Now, it doesn't work anymore, in either direction.

I use 1.2.5b1 on an Intel iMac running Tiger.

According to #p4533 this should have been fixed in Libpurple, yet Adium -> Adium transfers do not work. Will be testing this later.

Hi, I just want to follow up.

I asked in irc that adium already using libpurple 2.5.0 and the p4533 are implemented in libpurple 2.4.0 I felt like the problem still exist (sometimes it work, sometimes it doesn't)

Could anyone clear up the status on this matter?

This is still broken in the current released Adium 1.2.5. I don't know what libpurple is. But for me, transfers to people with real Yahoo do not usually work. Sometimes they do. Most times, Adium says the file is transferred, byt th remote person never receives a request.

I have no idea where the file goes. Maybe this is a security issue?

When testing this, ensure you are using the latest version - including betas (see AdiumBeta). That 1.3 beta release is the only one available with Libpurple 2.5.0 included.

The link is dead for the latest beta

Patience, young padawan.

Not that dead. Do any of you want to be my partner in testing. I just install the 1.3b1

Ah so the libpurple 2.5.0 update is in 1.3b1

Ok mass sending using 1.3b1 to: -7.5.0.814 -8.1.0.209 -8.1.0.402 -8.0.0.711 -9.0.0.907

Some other users haven't reply me their version number. 1. Might still not working 2. I'm amazed how many version number YM have

This still does not work with the 3.0 beta3. On my end, it claims the file is sent. But the person on the other end (with real messenger) never gets a request to accept a file, and cannot find the file on their PCs. So where did the 25 files I transferred go?

He was using 8.1.0.4.2

8.1.1.421

Adium 1.3b3 is able to receive files from other Yahoo! users, but still unable to send. The transfer looks ok on the Adium side, but the Yahoo! user does not receive a file transfer request.

* Other Yahoo! users are only Windows Based Yahoo! clients (version seems to not matter).

I have yet to find someone using Adium to test the file send between Adiums using Yahoo!.

Can one fetch the URL when uploading to filetransfer.msg.yahoo.com? I think I remember in the past when using a Yahoo! Messenger for Windows, sometimes when transfers would fail the file would upload to the Yahoo! servers and then provide me with a link. Does anyone know if that's still available?

Is there a way to build a script that will FTP the file to a personal FTP server and then paste the link in the IM? (that's a question for myself and google obviously, but I know that there are some really good coders out there that can code that in 1 hour, rather than me trying to in one week).

I'm on Adium X 1.3b9 Mac OS X 10.5.4 Intel, and Yahoo IM (YIM) transfers from myself to others who are using Yahoo messenger are not going through to them successfully. However, Yahoo users can files to me just fine. The Adium Yahoo dialog states that the transfer occurred, however, it is not the same dialog as say an AIM file transfer dialog. My Adium Yahoo account gives a transfer initiating message, then transfer sent. It does not give the waiting, direct connect IM to such-and-such IP, initiating, then transfer sent as with AIM. If anyone wants help testing, I'm more than happy to assist. I can try the Yahoo Messenger Mac Beta or Adium Yahoo account. But, to help with the Windows Yahoo Messenger, I'd have to do that through a VM session. This is a really annoying issue. So, it will be great when it is fixed. Thanks in advance.

Adding to this. All file transfers on all chat systems fail to all buddies/contacts/whatever on all networks. Transfers fail weather done from menu or by drag and drop to the chat window. Tested with multiple file types including jpg and mp3. Using the standard chat clients for the protocols always works. Adium is and has been unable to send files at all to anyone for several versions. It used to work some time ago, but I can not verify which version broke sending files. On yahoo it claims it sent the file but the other end never gets it. On AIM it always says the other end canceled when they did not. I am seeing other tickets of this nature deleted with no explanation why. This is a major global bug that has been present for over six months and 4 versions. It would be great if this was fixed because as is we constantly have to change clients just to send files.

Ditto on the last comment. Now NO FILE TRANSFER WORKS. What is happening here? It is getting worse, not better. This is with 1.3b11. It certainly cannot be released like this.

ebonweaver and jarome,

Adium is a really cool piece of software and great design work. Unfortunately, it is not Adium you should be mad at, but libpurple - it is the DLL (windows talk) or library of instructions for connecting to chat servers. Libpurple is the one that will hold this project down and finally kill it. All of these "extra" messengers that did not offer the full feature set of their original counterparts eventually faded away. Ever heard of Trillian? They are now trying to pull off one more comeback by using the iPhone.

So every time you see a bug report being "closed" down it just means there's nothing you can do on Adium's part of the code. Sad, I know.

Well, file transfers used to sometimes work, so maybe Adium should go back to the older libpurple version. Now they never work.

Where do I complain to the libpurple people?

#p6382 is the only report of Yahoo files transfers failing in Pidgin. It refers to only transfers between Pidgin users (and assumably any other libpurple users).

Here's what you need to do to get us the correct information in order to fix this file transfer bug:

1. Make sure you are using the latest 1.3 AdiumBeta.
2. Connect ONLY to your Yahoo account.
3. Turn on Debug logging and attempt to send a file to another libpurple (Adium 1.3b or Pidgin) user. Attach the debug log here. (Do NOT paste it in the comment box).
4. Turn on Debug logging and attempt to send a file to a user of the latest version of YIM for Windows. Attach the debug log here.
5. Find yourself a Windows box somewhere (use Parallels, or VMware if need be) ... surely one of you are going to have an Windows box you can use. (Linux works too). Download Pidgin and install it, then try to do a file transfer to another Pidgin or Adium 1.3b user; comment here with the results. Also try this with a user of the latest Windows YIM client and report the results here.

If needed, you can add me to your Yahoo contact list (same username as I'm using here) and I can help with your testing.

Please make sure that when you post a comment with useful information (such as the results of what I requested above) you explain everything clearly and in proper paragraph structure... there is a lot of different information being requested here, and I do not want to see it get so mixed up and confused that our developers can't gather the info they need from it.

Debug log includes:

1. An attempted transfer from jarome to myself
2. An attempted transfer from me to jarome

When I dropped the image in the chat window, it popped up the transfer window, showed the transfer completing in about 2 seconds, while he saw nothing on his end. He says the same happened when he sent the file to me. The debug log shows that Adium on my end saw his file transfer request, but seemed to do nothing about it.

1.4svn debug log

Please file a ticket in libpurple's trac and note the ticket number here.

http://developer.pidgin.im/ticket/7093

#p6749 was closed, so it would cool if you could test 1.3.3 once a beta is released. :)

I just tried 1.3.3b1. Yahoo file transfer STILL does not work. I can transfer in AOL and MSN, but Yahoo still never notifies the recipient that a file is coming. TRhe file appears to transfer, but goes into the bit bucket. This is a year now. It used to work before libpurple.

There was no Yahoo support "before libpurple" (back in 2004).

Then libpurple regressed, because Yahoo file transfer used to work. But this problem has persisted for a year now and needs to be fixed. And yes, I updated the pidgin bug. And pidgin displays the same problem.

It might be more effective to comment on #p6749.