skype4pidgin icon indicating copy to clipboard operation
skype4pidgin copied to clipboard

File Transfers Do Not Work

Open clone42 opened this issue 10 years ago • 13 comments

I have tested file transfers via Skype > Pidgin, Pidgin > Skype, and Pidgin > Pidgin. In all cases the file transfers fail. File transfers Skype > Skype succeed. Neither user is connected through a proxy or any network tomfoolery.

Skype > Pidgin: Pidgin reports: The user sent files in an unsupported way Skype reports: It just sits there waiting for the user to accept the file transfer.

Pidgin > Pidgin: To the sender it appears as if the file transferred and was completed. The progress bar even reflects that the file is transferring at the expected speed (tested with different file sizes). With a small test text file the receiving user receives this error: "Error reading from nus1-api.asm.skype.com: response too long (4 bytes limit)" The small text files do not actually transfer, (despite the chat log claiming completion - "Transfer of file test 2.txt complete" - their file names appear in their receipt folder, but as 0k empty files.

With larger files, like an mp3, the receiving user receives no prompt to accept the file, but the file appears to transfer from the perspective of the sender. In this case the receiver does not even get a 0 k empty filename.

The transfers appears to use bandwidth, but go nowhere.

Pidgin > Skype Same as Pidgin > Pidgin. In Pidgin it appears as if the file is transferring, the receiver gets no notification or file.

clone42 avatar Apr 02 '16 00:04 clone42

Same happens here

VelvetShadows avatar Apr 28 '16 01:04 VelvetShadows

I have same ussue and it's terrible! D:

Monsterovich avatar Jun 01 '16 14:06 Monsterovich

Today I accidentally received big file sent from Skype client. The only issue is that file was cut. Original size was 36.207.484 but I got first 36.204.544 bytes (size rounded down to 4096 bytes)

eschava avatar Jul 01 '16 11:07 eschava

I have same thing with any file.

Monsterovich avatar Jul 01 '16 14:07 Monsterovich

Also I cannot remove received file because it is still open by Pidgin process

eschava avatar Jul 14 '16 10:07 eschava

I have the same issue as eschava, the plugin downloads the content of the files, but the file size is cropped down from 385896 to 385024, which is again the size rounded down to 4096 bytes.

Penaz91 avatar Aug 25 '16 20:08 Penaz91

Still present on lastest debug dll..its a little annoying always have to open skype client to send/recieve files/images...

Error al leer de nus1-api.asm.skype.com: la respuesta es demasiado larga (el límite es 69 bytes)

By the way... aside from this bug...its working awesome. Thanks!

maxtros avatar Oct 29 '16 18:10 maxtros

Maybe it will be easier to just message file URL instead?

ssbb avatar Nov 03 '16 20:11 ssbb

Any chance to fix this issue?...right now i have to admin its working great, not even a single disconnect and always reconnect without problems (when I suspend my notebook and resume it)

maxtros avatar Jan 15 '17 18:01 maxtros

Same here. Seems files are truncated by a buffer chunk size. This might be in skypeweb_got_file function.

Q-Master avatar Feb 15 '17 06:02 Q-Master

Tried to transfer files from Pidgin to Skype. On Pidgin, it shows as if it had succeeded. On Skype, nothing shows up.

lmfardin avatar Sep 12 '17 19:09 lmfardin

if 1.1 is your plugin's version then it's ancient, upgrade and try again.

ildar avatar Sep 13 '17 10:09 ildar

Sadly this seems to happen also on the latest Git version, when I try to send files 1 second passes and then it returns "Transfer cancelled", while the partner doesn't get any request. There are no signs of errors (or even transfer-related debug lines) in the debug window.

If the conversation partner sends me a file, no dialog will pop up until their transfer is finished, then the transfer window will pop out and transfer the file successfully (even though I had no progress bar and only a "waiting" status on the tranfer). The file is whole and not cut to a multiple of 4096 anymore.

I'd say this is not just a 1.1 issue.

An upgrade is in order if you're using a version older than 1.4 anyway.

Penaz91 avatar Sep 13 '17 10:09 Penaz91