New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uploading not working at all in 2.2.2, and no error shown #730
Comments
(Maybe this is what entirely broke uploads: 07c94f2 ) |
Seeing same issue. 2.2.1 works fine |
Same here: Open keepassx database from the Seafile browser, modify one entry, close out back to Seafile browser - the file does not get transferred to the server. In aLogcat: the log show D/SeafileObserver: ......./SomePwSafe.kdbx was modified! |
I downgraded to 2.2.1 and it works perfectly there. |
Upgraded from 2.2.1 to 2.2.3 to test, and here I can upload new files, which is different from the behavior I initially reported about 2.2.2 (assuming that was fully accurate), but I still cannot change files. Replacing/updating existing files still does not actually change the files, all as initially reported. |
Bump, I'm also having this issue. And because the webclient requires logging in and out each time, it's getting very annoying. |
I wiped my phone and reinstalled Seafile, having forgotten about this issue, and of course uploads were still completely broken in the latest version. |
We are rewriting the uploading related code to solve several issues, this will take time. You can use the version in Google PlayStore which can work. |
Is there a reason not to revert the broken builds in F-Droid, other than the user base being small enough not to care? New users won't know they need to install an older version and not everyone even has the Play Store. |
F-Droid is build automatically. |
We have uploaded version 2.2.4 to GitHub. Can you try if you still have the upload problem? |
Can't truly verify since the phone which produced the issue is send for repair for a new screen. But it works for my very old replacement phone. I want to verify it again (and I likely will) when I've my daily driver back. |
Working on one of my phones. I tried adding a file (share/send to), and editing a file and both were transferred from phone to server.
I will try second phone later.
First phone is:
OnePlus One running
ResurrectionRemix
Android Nougat 7.1.2
Ivan
…On June 6, 2018 1:47:27 AM EDT, Daniel Pan ***@***.***> wrote:
We have uploaded version 2.2.4 to GitHub. Can you try if you still have
the upload problem?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#730 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Also seems to be WORKING on my wife's phone: (Probably unrelated?, but when I click a text file, Seadroid downloads but then doesn't offer the Text Viewer or Editor. Perhaps the text editor was installed by something not on my wife's phone. Anyway, when I changed the file using the Files program, Seadroid uploaded it.) |
Update: I got my daily driver back (Android 7). It works again. It works also well on another device I had my gasp on (Android 8.1). |
Uploads aren't working in 2.2.2 (F-Droid version, at least). I tried clearing data and clean reinstalling 2.2.2 multiple times. Creating (via Seafile) and editing a new text document, changes don't result in a successful upload. Document stays at 0kb and reopening shows it empty. Same for Keepass2Android databases; unfortunately I lost changes due to this.
This affects both attempting to open a file through Seafile itself or through the storage facility. Manual uploads don't work either, although they appear to. New file uploads don't actually appear. I can try to upload a file and replace an existing one and it asks to overwrite, and it says it updated, but no change occurs.
No error is reported by the app! The files on the server simply don't get changed, and their modification dates don't change either.
Reverted to clean install of Seafile F-Droid version 2.2.1 from December and the described tests work as expected.
Server was 6.2.4; updated to 6.2.5 and no fix. (x64, Ubuntu 17.10)
The text was updated successfully, but these errors were encountered: