zmjdx / swiftp

Automatically exported from code.google.com/p/swiftp
GNU General Public License v3.0
0 stars 0 forks source link

SwiFTP on Donut #13

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. install Donut on your phone
2. install SwiFTP ;)
3. connect to your SwiFTP Server

What is the expected behavior? What do you see instead?
Normally I would see the files stored on my sdcard, instead I see nothing 
:( Like my sdcard was empty (it isn´t!).

What version of the product are you using?
1.11

Please provide any additional information below.
I´m sure it´s because of new restrictions when reading / saving data since 
Android 1.6.

Tom

Original issue reported on code.google.com by tomtasche on 19 Oct 2009 at 4:56

GoogleCodeExporter commented 8 years ago
Tom, can you report what the server log says at the time of the problem? This 
is on
the main SwiFTP screen, you should see it when the server log checkbox is 
checked.

Thanks, Dave

Original comment by Dave.Revell@gmail.com on 19 Oct 2009 at 5:24

GoogleCodeExporter commented 8 years ago
Sorry for the late response, thought I would get a mail on new comments.

At the moment I don´t have a chance to test SwiFTP. I´ll try as soon as 
possible!

Original comment by tomtasche on 24 Oct 2009 at 10:45

GoogleCodeExporter commented 8 years ago
Ok, I tried on Ubuntu 9.10 and Windows Vista.

Ubuntu 9.10: (see attached: swiftp_karmic.png)
looks like sdcard is empty
but I can drag and drop files on it

Windows Vista: (see attached: swiftp_vista.png)
all folders shown, but with very strange names (in format: CHANGEDTIME 
FOLDERNAME)
when I want to open a folder, an error occures

I can´t say if it appears since I updated to Ubuntu 9.10 or Donut / 
CyanogenMod 
4.1.999. Updated at the same time :/ Sorry.

Any further information you need?
I didn´t see anything useful in server log: "authentication completed, ..."

Tom

Original comment by tomtasche on 27 Oct 2009 at 12:15

Attachments:

GoogleCodeExporter commented 8 years ago
Any progress? :)

Original comment by tomtasche on 13 Nov 2009 at 12:31

GoogleCodeExporter commented 8 years ago
I wish there was progress, but.. none right now. I'm hoping to release the new
version of SwiFTP over the holiday break, and hopefully this bug will be fixed 
at
that time.

My schoolwork has kept me extremely busy, so there's been no time for side 
projects.

Sorry,
Dave

Original comment by Dave.Revell@gmail.com on 13 Nov 2009 at 5:03

GoogleCodeExporter commented 8 years ago
This is same an encoding issue like in FTPServer
http://groups.google.com/group/andreasliebigapps/browse_thread/thread/8b3f10baf1
98f790

Original comment by g0n0gate@gmail.com on 28 Nov 2009 at 11:28

GoogleCodeExporter commented 8 years ago
This is hopefully fixed by the UTF8 FEAT fix.

Original comment by Dave.Revell@gmail.com on 4 Jan 2010 at 7:54

GoogleCodeExporter commented 8 years ago
What is UTF8 FEAT fix? Can you give us a link?. Thanks

Original comment by hwgonza...@gmail.com on 5 Jan 2010 at 2:41

GoogleCodeExporter commented 8 years ago
Sorry for the lack of info.

The fix that I mentioned is an unreleased change to the source code that makes 
SwiFTP
handle UTF-8 encodings of characters. The next version of SwiFTP will be pushed
through the normal channels soon (within a day or two) and will contain this 
fix. No
action should be necessary on your part until you see the normal Android update
notification.

Regards,
Dave

Original comment by Dave.Revell@gmail.com on 5 Jan 2010 at 2:45