-
Notifications
You must be signed in to change notification settings - Fork 278
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
Image uplaod not working #883
Comments
Using seadroid 2.2.33, I am also unable to make image upload work. I've tried triggering the sync manually, with no more success than the automated upload that is supposed to work. @bellegarde-c Could you share with me how you obtained these logs? Are they stored by seadroid on the phone storage? |
You need to enable adb and then launch adb logcat |
Thanks, that worked. Unfortunately, I cannot find a similar exception as you, and overall my logs do not contain anything wrong concerning seafile. But automatic image upload still does not work on my device, it seems stuck at "Upload info: Scanning". |
I am on seadroid 2.2.34 (MIUI global 12.0.4) and my upload info status stuck at "scanning" stage too. Automatic image upload does not work for me. EDIT: It seems image upload is working now , although the scanning stage took way too long ( 10 minute ) so I thought it is stuck. |
In my case the app has been installed and configured on my phone several days ago (thus much more than 10 min), and unfortunately no photo has been uploaded since then. Whenever I look at the Upload Info, it says either "Scanning" or "Upload waiting" (while when I wrote my previous message I thought it was only stuck at "Scanning"). |
Please update the latest version |
On the one hand, there are many photos in the album, and it takes time to scan whether the album matches have been backed up. On the other hand, due to the performance of the mobile phone, it is normal for the above to take a lot of time. |
I've upgraded to 2.2.34, but the problem remains. |
Delete the local seafile cache directory (under the root directory or /Android/data/com.seafile.seadroid2) and reset the backup file |
I understand that it takes time to scan my gallery for changed files, It is just strange to me, that with previous version of the app (Seafile 2.2.31) the scan takes about 1 minute to complete, not 10 (or more). |
I have deleted the seafile cache directory, but the problem remains. Could you tell me what you mean by "reset the backup file"? |
Clean up app cache files,Reset the upload file |
The picture and the video are scanned separately, maybe when you see it, the picture is scanned, and then the video is scanned. |
I've cleared the app cache + deleted the local files + deleted I've also tried uninstalling and reinstalling the app, but that did not change anything either. |
What is your phone model and Android system? |
Xiaomi Mi Mix 2, LineageOS 17.1 + microG |
After checking today, for some reason the Upload Info is not Scanning anymore, and is now Last sync finished at 04-11 11:19. But I have checked and unfortunately exactly zero pictures have been uploaded. I've manually triggered a new sync, and now it's once again stuck at Scanning. |
Hello, I've got the same problem with latest app 2.2.34 from F-Droid repo on my two Asus Zenfone Max Pro M1 running LineageOS 15.1. In settings, the app is Scanning for updates to upload, then it hangs (I'm unable to scroll up / down in the settings screen) and then it displays Last sync with current timestamp but nothing has been uploaded. I was running Seafile Server 7.0 so I upgraded to 8.0 but with no more success. After clearing the in-app cache and system's app cache, the behavior has changed: app displays Scanning, then crashes. Upon restarting, app displays Upload waiting while network is up, then starts scanning and crashes again after down/up the wifi. Last uploaded picture is from late January on both phones using the auto upload feature. But then I've been having an issue with the upload feature: I had to manually launch it so it starts scanning and uploading images. So maybe the late January date is not really reliable. |
More details: upload works properly when I deselect the relatively large Camera folder (2090 files) from the scan folder list. |
same problem with Seafile-2.2.35. from adb logcat, get nothing log from "seadroid-2.2.35\app\src\main\java\com\seafile\seadroid2\cameraupload\CameraSyncAdapter.java" with Utils.utilsLogInfo function. and I create a new accout for albums sync test with Seafile-2.2.35 and linux server 8.0.4 64bit. after scan finish, every album make a directory in server, but no any files are uploaded, all directories are empty. but Seafile-2.2.31 is ok. |
Upgraded to 2.2.35 and picture+video uploads broke. I removed my account, cleared cache, and wiped app data -- uploads still broken. Scans run, finds no files to upload. I've tried pointing it to a new server-side library as well. Downgraded to 2.2.31 and photo uploads are working again. No videos are uploading, still. |
I have the same trouble on my Samsung A72. After downgrade to Seafile-2.2.31 all photo and video uploads normal. |
I've upgraded to Seafile-2.2.36 today, but unfortunately the problem remained. However, I can confirm that downgrading to Seafile-2.2.31 does solve the problem! For the first time ever, automatic upload has started on my phone! 🎊 |
Same here, downgrading to Seafile-2.2.31 surprisingly worked. All later ones are broken. |
Not to be redundant but same here. Tried to delete cache, upgrade to 2.2.36, nothing. Tried to downgrade to 2.2.31 and it worked! It took 15-20 hours to fully sync but it worked. |
Same issue here. In 2.2.36 auto uploading not working. When downgrade to 2.2.31, auto uploading start working, but it reuploads all things that were uploaded before. On the server side, the new uploaded photos are named as xxx_(1).png |
Thread outlining the same issue on the forums https://forum.seafile.com/t/android-2-2-32-camera-upload-failed/13708/ It reminds me of #800 which @freeplant solved previously. Perhaps it's a regression bug? Hopefully this is something that can be resolved. I don't mind helping to debug/test! |
As outlined in the forum threads, this issue has been fixed for me in 2.2.39 after disabling and re-enabling camera upload. |
Please update the latest version |
Looks like it fails to access my photos:
OS : LineageOS 17.1
The text was updated successfully, but these errors were encountered: