- Android version: 9
- Joplin: 1.0.316
- Backend: file system + Nextcloud to sync folder
- Nextcloud version: 3.10.1 (client on Android)
I'm having issues with android sync with the file-system back-end:
Last error: TypeError: null is not an object (evaluating 'n.stat.size')
The closest topics to my issue are those:
I checked and there are no 0B objects in my folder that Nextcloud/Joplin use. I double checked on Linux with the file browser. I can't find the culprit, because in Joplin's logs there are no UUIDs mentioned for this error in the Android logs from within Joplin.
I used this:
~/Applications/Joplin-1.0.179_00000000000000000000000000000000.appimage --profile ~/joplin/temp --stack-trace-enabled --log-level debug --open-dev-tools
to run Joplin in debug mode and I had no sync errors. The performance is awesome and all files get synced from the file-system back-end and decrypted.*
*I had to rename my profile in ~/.config because despite the --profile flag Joplin would attach to the existing profile. Or maybe this is how it's supposed to work?
Please tell me, what;s the preferred method of wiping local data for Joplin on Android? On Linux I just rename the profile folder in ~/.config and start Joplin again. On Android I used the built in "wipe application data" button to manage space. Could this be the cause?
One more thing: I used the Nextcloud back-end on Android previously, because Nextcloud had some issues with sync. But without any reasons they normalized. I then (without wiping data) switched to the File System back-end. Could this be the source of the issue?
Thank you for creating and supporting Joplin!