I am running grapheneos and got nc from fdroid if it matters. I also use nc on my local network only.
I've run into this when one person on a network is using Linux or Mac, and another Windows. They have different filename rules.
I stopped using nextcloud after syncing suddenly broke for me, but in the app on my phone I could pull up the list of files with sync errors. It should be somewhere in the sync setting section.
If you're running nc locally, check the logs, maybe there's something relevant in there.
Another thing to check is the file path. Most systems abide by a 255 character limit and that limit can be crossed by parent folders having too many words in them.
This is the way! Slowly replace Nextcloud components with better things until you're no longer dependent on it
I really want to like Nextcloud, but it had way way too many issues and limitations for me the last time I set it up (May, I think?)
What a negative post without any proof. This issue might've even been old and not related to a recent update. The post you're quoting actually has a comment showing that this might be a bug already reported in 2023 https://github.com/nextcloud/android/issues/12137. In that sense a future update might just fix this problem. Also take a look at the changelogs of Nextcloud. They don't just contain new features, but also many fixes and improvements/rewrites of old code to make things more stable, more maintainable and faster.
If you've been updating to new major Nextcloud versions right after release: stop doing that. Wait several point releases and updating becomes really stable.
Eek, I'm moving towards nextcloud (and away from Google fast as possible). Is there a better all-in-one groupware + files + collab + office apps suite out there?
It does appear that nextcloud's devs are eyeballs deep in php tech debt, so their pace of development and integration has slowed.
It's so big that none of their FOSS components are going to be #1 on their own.
Recently upgraded the version and had to allow untested app versions (which had just disappeared) because they hadn't been updated yet. That's a weird problem and yeah, I don't really want to be beta tester everytime I try and open a document.
They also don't really have a nice docker compose based deployment yet.
But I couldn't be happier to be leaving google in the dust, so there's that.
Looks like it's a bug: https://github.com/nextcloud/android/issues/12137 and it's not yet fixed, unfortunately.
all 12 comments