You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
V35.0.2 auto upload does not work on my FP3 (Android 11) #17987
As stated in #5610 in a side comment on that topic, what was not working in my tablet (android 9) is obviously working on my FP3 (Android 11). That means: I can configure auto upload with deletion of uploaded files on both, external card and internal memory. But neither does upload automatically, although trying regularily (as what the Banner "Nextcloud: Uploading...." shows.
What's redicolous - at least the auto upload on internal memory on tablet is working against the same destination and with the elder version 34.1.0. As needing this feature, I don't update this partial working instance to 35.0.2 or the like.
Total Commander can do all file operations on both, the external card and the internal memory's directory.
That files are inside that directory is shown, when switching to that "auto upload" dir in configuration panel
Expected behaviour
Working auto upload as configured on both - the external card and the internal memory with deleting the uploaded files afterwards.
Actual behaviour
upload is regularily tried (from notification banner), but does not do its job.
Android version
Android 11
Device brand and model
Fairphone FP3
Stock or custom OS?
Stock
Nextcloud android app version
35.0.2
Nextcloud server version
34.0.5
Using a reverse proxy?
No
Android logs
found /data under /Android/data , opened the right app (com.nextcloud.client) - the only fitting FQN, but there is no logfile inside.
I created PR to understand the issue better. Once the QA APK is generated could you please download the APK and share the logs?
You can access logs from Settings -> Logs and filter by isFolderWritable.
To test you can open dialog that has “Original file will be...” option then see if it's still not selectable. Just like you explained here: #5610 (comment).
I created PR to understand the issue better. Once the QA APK is generated could you please download the APK and share the logs?
You can access logs from Settings -> Logs and filter by isFolderWritable.
To test you can open dialog that has “Original file will be...” option then see if it's still not selectable. Just like you explained here: #5610 (comment).
I installed this app (in parallel to the release version) and configured the original external directory for "auto upload" with deletion of files after their upload. Could select this option as in the V35.0.2 - which see same directory and its content, but do/did not upload it all the time.
The QA-Version is working as expected, directly after having configured the new auto upload (outside every "found" image directories, which are put in "inactive"), the upload took place, then the deletion took place and as I could see from notifications, it's regularily checking the dir (also same as in V35.0.2). I'll "feed" another file and see if new files there are handled the same.
Activity
alperozturk96 commentedon Nov 9, 2026
@itsbrody Hello,
I created PR to understand the issue better. Once the QA APK is generated could you please download the APK and share the logs?
You can access logs from Settings -> Logs and filter by
isFolderWritable.To test you can open dialog that has “Original file will be...” option then see if it's still not selectable. Just like you explained here: #5610 (comment).
APK will be available here: #17996
itsbrody commentedon Nov 10, 2026
@alperozturk96 , thanks a lot for your efforts
I installed this app (in parallel to the release version) and configured the original external directory for "auto upload" with deletion of files after their upload. Could select this option as in the V35.0.2 - which see same directory and its content, but do/did not upload it all the time.
The QA-Version is working as expected, directly after having configured the new auto upload (outside every "found" image directories, which are put in "inactive"), the upload took place, then the deletion took place and as I could see from notifications, it's regularily checking the dir (also same as in V35.0.2). I'll "feed" another file and see if new files there are handled the same.
Here are excerpts of log