-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
"Content Unavailable" error for folders with many items #252
Comments
Hi. Actually this error might not be about the number of files anymore but what @USER19464727 describes. My folder now have almost 5k files and I haven't seen the issue ever since. It does take a lot to open the folder though, about ~5 minutes. |
The long loading time depends on several things like the used cloud provider and your internet connection. The problem is that it's not possible (without using the working set, which we do not use because of the security implications) to show partial results. Even if we would use the working set we would still have a bad user experience as there is no indication of an ongoing loading process in the files app. Furthermore, the items would just "randomly" show up in chunks because we can not apply the selected sorting rule before all items are processed and therefore the new items would not even appear at the end of the list / grid. However, we should definitely investigate the error described by @USER19464727. |
It happens to me too, and with folders already "set as available offline" and 100% downloaded. As soon as my photo folders have more than 250-350 files, the message is shown on Files App. Let me know if you need more information from me. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
While trying to address the ticket, I found that I couldn’t reproduce the error. I uploaded approximately 600 photo and video files to Nextcloud via WebDAV and followed the description provided by @USER19464727, but I did not encounter the expected bug. Is the error still occurring on your side? |
I am no longer a user, so I'm not sure if it is fixed, sorry. |
@USER19464727 Thank you for the update! It’s unfortunate to hear that you’re no longer using Cryptomator for iOS, but we appreciate your honest feedback. |
Follow-up of #232 by @serranomorante:
The text was updated successfully, but these errors were encountered: