Sorry about the messed up snippets from above
I've edited the file through the Desktop-App and the Android app (no manual edit). I don't exactly remember on which platform I made the edit which broke the file but I think it was Android.
I have hand edited the file to make it match the other working files and the error is gone. I then revesed my changes through my Android phone and the error has reappeared. It looks like the culprit is that the app appends type_: 1 twice at the end of the file. Remove the second appearance and it works.
had to redact a bunch of stuff, hoping I didn’t eliminate any text/formatting that might have been the source of the error(s)
DAILY TO DO
work on XXXX
find XXXX bio
install resilio sync on doze side
note to XXXXX
copy Weininger to thing Kindle?
copy audiobooks!!! to player
rig Joplin on other laptops
work on RP
play with tethering, only to check shit out
Greg & XXXX
XXXX tutorial adding fade ins dissolves, titles
artwork for Faile
do that XXX access thing that stupid $35 thing eh
look at script
take up kraut
find out how long you can leave it down there as well
change the conflicted copies dealie with Dropbox, or maybe just stop using it
get popel bars
check Met HD for dates
find old set lists please
fix vim thingie
write Teddy B
today - submit to more festivals
write Al B
archive MGA stuff onto website
I don’t believe I did, at least until the error appeared: I think I removed a line near the very top because I thought it might have been the source of the Joplin error, but it’s highly unlikely I would have added that line.
The Android version of ResilioSync – that’s what Syncthing is called now – seems to me not as reliable as the Linux or Windows versions: for instance, I believe I have to go into the app to get it to perform a sync. While I have only been using it for several weeks – likewise, I am also very new to Joplin – I haven’t experienced any issues, apart from this
Don’t know if it’s pertinent, but I have seen conflicts arise thanks to my multiple backup strategies: DropBox as well as pCloud, though usually these create copies with filenames containing [conflicted]. Possibly a problem created by edited the same file in different sessions?
Can I just remove the line containing “type_: 1: 1” and proceed?
The way your file looks now is as if something had overwritten the file, but left the previous content at the end. Not sure if it's syncthing but I'd be careful and try to find the cause, if you don't want to lose your data.
Deleting that line seemed to fix things for a while, but I'm having numerous other problems trying to get the Android version running with Resilio Sync -- I suspect it's essentially this issue
The Linux versions sync well with Resilio Sync -- for those of us trying to get away from commercial services, Resilio (which used to be called Syncthing) is a great solution, it uses BitTorrent to sync directories.
This morning I tried to see if I could get Joplin/Android working with Dropbox, but failed, unfortunately. If there is a recommended way to get this working, I'd be happy to try it.
I’ve been having the same issue. I’m using syncthing between joplin on android and linux. The problem is on the android side. I think syncthing and joplin are trying to write to the same file at once. I’m doing some further testing.
I am also having the same issue. I am using Syncthing and Joplin on Android. I really like Joplin so far, but this bug makes it hard to be completely confident that my data will stay intact.
Edit: I have searched Syncthing’s issues and forum and no one seems to have mentioned this over there. I would try create a post, but not sure I can gather enough info to make a meaningful bug report.
Edit2: After thinking about what @laurent said about leaving previous content at the end, I tried making a simple note in Joplin and then deleting a line to make the note shorter. This immediately triggered the problem.
Test syncthing and joplin
This is a note to test what is corrupting my notes.
type_: 1: 1
@laurent, Thanks for your replies. I have started a thread in the syncthing forum and one of the syncthing maintainers has responded. I will try do my part to go between as needed, but I am not certain I can answer the questions accurately.
One important point is that Joplin has been used with many sync clients, such as Dropbox, OneDrive, Nextcloud and many others for several years, and this particular issue only happens with Syncthing. I’m mentioning this because it would be easy to assume Joplin writes to the files in a strange way, but it’s not like this, or it would happen with all the other backends too.
Syncthing triggers when android announces that a file has been changed. Then it syncs it with the other devices. Does anyone know how android handles file updates? Does it announce when a edited file is closed or when data is written to a file? Because the issue only happens on an android device.