Android has stopped syncing via Filesystem and Syncthing.
I noticed it today when I created a new note and waited for sync to happen. All my other clients are still syncing fine.
Attempted so far:
Verified Syncthing is working properly.
Attempted clear cache and data from Android App
Attempted removing and reinstalling Android App
Symptoms:
When sync begins it counts off the first 50 to 250 items as "created local items" and "Fetched Items" and moves at a few items per second. After it begins to count off 50 items at a time at about 100 items per second. This continues forever. I've let it run to 25000 items on an installation with 343 items.
Canceling does not show imported items.
When I started I had 258 items, 5 folders, and 28.1MB according to Syncthing and 125 notes, 19 folders, 65 resources and 134 revisions for a total of 343 items. Syncthing has now grown to 408 files, 5 folders 46.9MB.
With every attempt my other two clients complain about 3 addtional files being created: SubNotebooks.png,
WebClipper.png, AllClients.png. These are in the index, but not on the drive. I can manually remove them from the index, and the complaint goes away.
The desktop clients are v3.6.14 linux.
What can I provide to help with resolving this issue?
Adding: I'm having issues getting images to sync between the desktops now as well. Both were just upgraded and didn't exhibit this issue before. Discovered this doing a step by step guide to how I reinstalled and re-synced.
These are an image on a laptop remote on v3.6.14 linux, and three demo images on the affected Android.
Downgrading Android to v3.5.8 made the three demo images available to the linux machines. After that the images between the linux machines worked with a retry. It appears that there is more to what is happening with Android 3.6.19 and it is getting into the index to write it's three demo images, which were already deleted on the device, and then failing to finish the sync.
Yeah it's likely the bug in 3.6.19 also affected resource uploads, so as it was a bug introduced in the file system handler. The next release should fix the cause of that as well.
From my perspective, it appears the index of resources was updated with the 3 "demo" resources from Android. What's odd about that, but possibly by design, is that those notes were deleted before the file sync was established. That explains WHY the resources were missing. As for the image from the laptop, that's a little more curious. The Android sync shouldn't have prevented or fixed the laptop and desktop syncing. I haven't had more time to look into it, but if I do, I'll update here. I suspect that there is something wrong with those versions as well and the older Android version is detecting and correcting that, but 100% guessing on that.
I wouldn't look too deep into this as it's complicated stuff. I'm 99% sure the issue was caused by a knock on effect of the bug which is being fixed.
If the list of attachments which cannot be downloaded has cleared itself then great. If not, or they come back, I can point you to a guide to delete the references to those attachments.
I encountered the same problem today: synchronization is no longer working.
In the process, I noticed the following additional symptoms:
Menu > Configuration > Tools > LOG > Share.
Result: The app crashes after a few seconds.
Menu > Configuration > Import and Export > EXPORT DEBUG REPORT.
The button text changes to CREATING REPORT...
Then I select a folder to save to. Then the app crashes.
Joplin Mobile 3.6.19 (prod, android)
Device: android
Sync Version: 3
Profile Version: 49
Keychain Supported: No
Alternative instance ID: -
Sync target: Dropbox
Editor: Markdown
@thimu I think the crashes when exporting the log is also a knock on effect of the bug introduced (various file access in the Android app may be broken).
If you have a lot of data, I'd recommend waiting until 3.6.20 is released, as you could spend a long time resyncing everything. But if you really can't wait, you can uninstall the app and then downgrade to 3.6.18 or below
