Error: Invalid property format: type: Hitoduma Medusa-san tono NTR

Operating system


Joplin version


Desktop version info

Joplin 2.13.15 (prod, win32)

Client ID: 4aaec9e59fe6455b9687d8c81b0e5bf7
Sync Version: 3
Profile Version: 44
Keychain Supported: Yes

Revision: 7d2c1c0

Csv Import: 1.0.1
Favorites: 1.3.0
Markdown Table: Sortable: 1.2.2
Math Mode: 0.5.3

Sync target

File system

What issue do you have?

I just sync to another directory (which gets backed up by pCloud).

I translate a lot of Japanese Manga for various groups, and about a month ago I did a gag manga about a cheating medusa wife and Joplin started throwing sync errors. I suspect it's because I initially named the note with Kanji and it doesn't know how to deal with that?

I did the How to enable debugging | Joplin thing, and got a log with errors, but don't see anything that tells me how to fix this - any help? Thank you.

Log file

log.txt (76.3 KB)


have you edit the md files in the SyncTarget where you have selected FileSystem outside of Joplin?
Because the file 29154f53183c464f9687d8b5a39464f5 is no longer valid, the type field is messed up.

Could you upload the 29154f53183c464f9687d8b5a39464f5 file.

1 Like

I had not, because I don't know enough to manually edit any of the Joplin files. However, with your info I was able to determine that pCloud had created a 29154f53183c464f9687d8b5a39464f5 (conflicted).md5 file in the sync directory, which was what was upsetting Joplin. Now I know to look for those, thank you.

Also is pCloud based on Nextcloud? Because simply opening a file in Nextcloud (without even changing it) is going to corrupt it. That won't be fixed as they consider it's working as expected...

Hi Laurent - I don't believe so. It's their own sauce, they've been around since 2014.

From experience, it creating a '(conflicted)' version of a file happens when it can't reconcile the cloud version with local changes - the three way diff fails so it creates the extra (conflicted) file so at least you don't lose anything. I've been using pCloud with Joplin for about a year now, syncing from Joplin to a directory that's pCloud backed up, and this is the only (conflicted) file so far. And now I know what to do if that happens again.

Handling conflicts is something that happens client-side which means it's probably the pCloud sync client that created that conflict file. I suppose it could happen but it could cause issues with Joplin's own conflict resolution algorithm.

When this happens, move the (conflicted) file out of the folder but maybe keep it somewhere in case it turns you need it to restore data.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.