Auto Upload stops working until You delete the "[email protected]/tmp" folder
⚠️ Before posting ⚠️
- [x] This is a bug, not a question or an enhancement.
- [x] I've searched for similar issues and didn't find a duplicate.
- [x] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [x] I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
- Enable auto sync feature with upload only on Wi-Fi
- Turn off the Wi-Fi on device
- Add new items to synced folder (for me it's photos)
- Wait for creating tmp folder
- Turn on the Wi-Fi
- Wait to auto upload newly added items
- Turn off again Wi-Fi on device
- Add another new items to folder
- Turn on the Wi-Fi
- See the issue (it won't upload new items for months)
Expected behaviour
Delete the tmp folder after uploading to normaly scan the initial folder for new items
Actual behaviour
I guess app is scanning only tmp folder until You delete it. After deleting he is automatically continue to auto upload.
Android version
15
Device brand and model
Realme 11 Pro+ (RMX3741)
Stock or custom OS?
Stock
Nextcloud android app version
3.34.1
Nextcloud server version
Nextcloud Hub 25 Autumn (32.0.0)
Using a reverse proxy?
No
Android logs
No response
Server error logs
Additional information
This isn't a bug, but an incorrectly working behavior, so no one (the application and the server) will not create logs about this
This may be (one of the) cause for recent autoupload lockups I've seen with other people (couldn't reproduce myself) I know the 3.35.0 release will include an improved logic on re-scanning and retries, but if this specific problem isn't covered already it would be amazing to have auto-upload get unstuck for a bunch of people.
Can you confirm this tmp folder is client-side? (on the phone?) It won't be easy to guide users to find them and remove them, so I hope 3.35.0 comes in soon and becomes able to mitigate or auto-resolve this issue!
Yes, this tmp folder is on phone, because i can access it from "Gallery" application and from "My Files" via the path "/Android/media/com.nextcloud.client/nextcloud/". This folder contains main folder for every downloaded files and the tmp folder.
I've been struggling with this problem since the summer of this year, and I've only just figured out the cause.
Pardon me but why is an incorrect working behavior not a bug?
I just feel the internet has given nextcloud too much leeway about how good it is when in reality, it is riddled with the same bugs that are still unresolved for years despite reworked on multiple times.. and more often than not, issues cannot be reproduced and logs almost impossible to find, and this is across macOS, Android and Windows.
Apparently they have finally changed the approach in 3.35.0, even then, that is only for 1 bug.
Try the DEV version. I've been testing it for 2 weeks now. Auto-upload seems to be fixed, finally! Good work everyone!
3.35.0-RC1 has been released and is available on the play story by entering the beta program!
Please report back whether it solves the problem of some of the numerous issues still need to be debugged with the new implementation! 💪
I just feel the internet has given nextcloud too much leeway about how good it is when in reality, it is riddled with the same bugs that are still unresolved for years despite reworked on multiple times.. and more often than not, issues cannot be reproduced and logs almost impossible to find, and this is across macOS, Android and Windows.
Well, I have tested 3.35.0-RC1 and it still doesn't upload my 3 files reported in https://github.com/nextcloud/android/issues/16027 and once again reinforces my observations shared above.
Whatever different approach described, made no difference to my issue.
Wonderful, 3.35.0-RC1 now refuses to auto upload anything........... 3+ 1 images now...... 🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️ so much for the different approach hype
Can you provide logs from the app? It would be helpful for everyone out here! 🙏
I have no idea how to get the logs
And how do I downgrade to stable..... I'm using obtainium
I have no idea how to get the logs
In the settings, towards the end, after "Help" and "Recoment to a friend" but before the "About" section
They seem extremely helpful, from what I see, it should help have a clearer view at why it skips files!
GOSH... ANOTHER BUG 🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️
I don't think it's a bug necessarily, but I've noticed that sometimes the log options is there and sometimes not, I thought it was down to having installed a beta version, but apparently it's not the only criteria?
My log option came back and has a ton of useful detail but I don't know the details of why you might not see it! I'm sure a dev can chime in
Found this: https://github.com/nextcloud/android/blob/ffe2cc1edd93bbeab8435b285e3de9a115953a24/app/src/main/res/values/setup.xml#L94
for main builds
https://github.com/nextcloud/android/blob/ffe2cc1edd93bbeab8435b285e3de9a115953a24/app/src/versionDev/res/values/setup.xml#L24
for dev builds
What's strangs is you're apparently on 3.35.0-RC1, which is obviously a dev build (same as mine) so you should have this boolean set to true. In trying to downgrade, might you have left the beta program or confused something in the process?
As mentioned, I'm using obtainium (not playstore beta), 3.35.0-RC1 download from fdroid https://f-droid.org/en/packages/com.nextcloud.client/
Other than BUG, I do not know what else to call it.
Now this is a bit offtopic but still quite interesting! Having a look at the f-droid build logs: https://f-droid.org/repo/com.nextcloud.client_30350052.log.gz
It seems their build pipeline is actually building Release candidates (here 3.35.0-rc2) as main instead of versionDev
This seems to suggest their CI is doing something wrong, or missing elements that this project uses in its build logic at github, and 100% explains the absence of the "log" entry in the f-droid build.
F-droid seems to be doing the mistake, in this case...
@bilogic if you still want to help with logs to understand what's going wrong, I think you either need to switch to google play builds or simply install the properly built apk from here
Bug in CI, who wrote the CI? f-droid or nextcloud? Can't switch as there is no migration tool https://github.com/nextcloud/android/issues/15542