cross-posted from: https://lemmy.world/post/36410134
cross-posted from: https://lemmy.world/post/36348624
I am running grapheneos and got nc from fdroid if it matters. I also use nc on my local network only.
So I could not find logs that pointed to any specific file giving the errors. Still I took the advice that it might have to do with file names. That made me suspect it had to do with my music folder which has some foreign music, so i renamed files with a special character. So far it seems that was it. This was odd because those files have been there and synced for a while, but the message was not happening until recently. Still wanted to update in case someone else has this issue there is some resolution that might be helpful.
So I couldn't really find what are the offending filenames, but they were from the music folder. I guess I didn't mention that that was the most recent folder I set as a two way sync. I get most of my music from yt-dl and naturally wanted to have it on both my laptop and phone. I since have discovered Power Ampache 2 . It is a music player and it can just stream and download your music on your Next Cloud. So far it works well and I have no more errors regarding filenames as I no longer need the Next Cloud app to do a two way sync.
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.
The update is from me and what I am doing in my selfhosting