Autoupload configuration page loads indefinitely

[ThaChillera]

Steps to reproduce

1. Configure a fresh autoupload folder with lots of files
2. While uploading, try to open the autoupload settings page
3. settings load take forever, phone gets very hot

Expected behaviour

• Settings should just load

Actual behaviour

• Loading takes forever

Environment data

Android version: 11

Device model: Fairphone 3+

Stock or customized system: LineageOS MicroG

Nextcloud app version: 3.20.1

Nextcloud server version: 24.0.1

Reverse proxy: nginx

[ThaChillera]

Update/correction: I got through the autoupload queue, but this issue still persists. I attached a debugger but didn't see any log lines that looked relevant

[ThaChillera]

I'm still experiencing this issue, 2 months later! any tips/info?

[ThaChillera]

Update: reset the app, configured auto upload again, issue still exists.

[moritzgloeckl]

I'm having the same issues would be glad if there was a solution! It seems though that auto sync is working in the background.

[ThaChillera]

Reproduced on latest release (3.21.1), issue still exists. I know nothing about Kotlin & Co-routines, so this might be entirely inaccurate, but I found the issue that my debugger never reaches this line: https://github.com/nextcloud/android/blob/master/app/src/main/java/com/owncloud/android/ui/activity/SyncedFoldersActivity.kt#L321 but it does start the coroutine (confirmed with debugger).

@AlvaroBrey any chance you or any other project member would have time to look at this?

[joshtrichards]

Configure a fresh autoupload folder with lots of files

How, precisely, did you configure it? There are numerous option combinations. Knowing this is important for reproducibility and bug triaging. Thanks!

Oh, and what do you mean by "lots"? 100, 1000, 10000? Etc.

Also, a log would still be helpful (either from inside a Dev version of the app under Settings->Logs or via LogCat with a standard version of the app).

Feel free to redact using search & replace as needed.

[github-actions[bot]]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!