Android Client Auto Upload fails to create new subdirectories.

[CakePost]

⚠️ Before posting ⚠️

• This is a bug, not a question or an enhancement.
• I've searched for similar issues and didn't find a duplicate.
• I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

In the Android Nexcloud app

1. Select Settings > Auto upload > hamburger button upper right > Set up a custom folder.
2. In the modal that appears, set the Local folder option to /storage/emulated/0
3. set the Remote folder option to InstantUpload
4. set Only upload on unmetered Wi-Fi to true
5. set Only upload when charging to false
6. set Also upload existing filestotrue`
7. set Use subfolders: Store in subfolders based on date to false
8. set Exclude hidden to false
9. set What to do if the file already exists? to Ask me every time
10. Click Save

Expected behaviour

I expect that all files and folders in the tree of folders starting at /storage/emulated/0/ be uploaded to Nextcloud with the same folder structure.

Actual behaviour

Observe that the app will successfully sync files and folders located in /storage/emulated/0 and also files stored in directories of /storage/emulated/0/*/
Observe that the app will fail to sync files and folders located in /storage/emulated/0/*/*/, i.e. any second-order or deeper sub-directory of /storage/emulated/0/ (the directory configured in the custom folder settings described above). The notification will will show the error Upload failed File not found.
Navigating to hamburger button upper left > uploads and scrolling to Failed/pending restart will show a bunch of files with the message Folder error. All of the files are located in second-order sub-directories of the custom directory configured (/storage/emulated/0/)

Android version

12, Build SP1A.210812.016.C2

Device brand and model

Google Pixel 3

Stock or custom OS?

Stock

Nextcloud android app version

3.30.8

Nextcloud server version

Nextcloud Hub 8 (29.0.9)

Using a reverse proxy?

I don't know

Android logs

No response

Server error logs

I'm using hetzner as a provider for the server. It seems they don't enable file-based logging and so I've filed a support ticket to try to get the error logs from them. Will update once I receive them.

Additional information

There does not exist the folder storage/emulated/0/data/ when looking through the internal storage of my phone. My phone is not rooted so I can't use logcat to obtain logs. As such, I can't provide logs unless there's further instruction on how I might be able to do so.

[CakePost]

Note, this looks like #3484 in many ways, but given the issue has been closed, this is either a regression of the original bug, or a new form of the same bug.

[CakePost]

The app has been looping on these uploads perpetually for days. I'm sure there's some useful logs to be gathered but I can't figure out how to get access to them. If someone can tell me how I can get logs from the nextcloud app without needing to root my phone I'd love to be able to upload them.

[NiklasBeierl]

I was observing similar issues with auto upload, signing out and back in with the app resolved them. 🤷

[CakePost]

Unfortunately Hetzner won't send me server logs. I'm trying to figure out how to use adb/logcat but I'm not finding a good walk-through on how to use it with the Nextcloud app. Once I can figure that out I'll add the logs. I'm abstaining from doing the workaround @NiklasBeierl mentioned as I'm sure the logs from the app may hold some info on why this is happening in the first place.

[CakePost]

This is as close as I've been able to get for grabbing the logs off from my device for this bug report.

$ ./adb.exe devices -l
List of devices attached
89WX0J410              offline transport_id:5

I can see my device listed but it's always "offline".

Running ./adb.exe logcat just leaves me with:

$ ./adb.exe logcat -v brief output
- waiting for device -

Apologias for this turning into more of a "how do I get the logs off my phone" thread, but I really do want to help resolve this issue since when I start rolling out Nextcloud for my family I want to know that it's going to be getting more reliable.