Operating system
Android
Joplin version
3.0.7
Desktop version info
Joplin 3.0.12 (prod, win32)
Joplin 3.0.13 (prod, win32)
Sync target
Joplin Cloud
What issue do you have?
Forked from
Today I picked out a second problem case and examined it more deeply with the help of the Joplin debug tool plugin 0.2.0, both on Android and on Windows: The message "Some elements cannot be decrypted" on my Android and the four IDs that are mentioned there.
Using the Android Joplin Debug Tool 0.2.0, I was able to determine the three notes to which these four graphic elements belong. I was unable to find these elements with the Windows Joplin Debug Tool 0.2.0 – I suspect that they no longer exist under Windows and in the Joplin cloud.
I had somehow repaired the three notes recently and was able to remove them from my conflicts at that time. Unfortunately, the same notes have broken again and reappeared in the conflicts.
I will now repair these three notes again or recreate them from the information that can be found:
First, I create a completely new note in the same folder as the defective note and use the same name plus the name extension - new from saved data
.
Then I copy the MarkUp content of the defective note manually into this new note in edit mode and replace the MarkUp text of the defective graphic with the MarkUp text of the still functioning note from an earlier version.
I hope that this problem will no longer occur. The reason for my hope is that I followed the advice to disable the OCR function. I even suspect that the current version of the OCR function not only generates a lot of load and thus causes conflicts. I suspect that the current version of the OCR function can also generate errors.
The reason for this suspicion is the strange markup text that I found in the faulty note.
In the good, restored note, this markup text reads
![32ddce2402b93faafeb7e27624585c09.png](:/582e16f384034024bc6979f5a5e5ccf7)
In the damaged note, this markup text reads
![](data:image/svg+xml;utf8,%0A%09%09<svg%20width="1700"%20height="1536"%20xmlns="[http://www.w3.org/2000/svg"> <path d="M1280 1344c0-35-29-64-64-64s-64 29-64 64 29 64 64 64 64-29 64-64zm256 0c0-35-29-64-64-64s-64 29-64 64 29 64 64 64 64-29 64-64zm128-224v320c0 53-43 96-96 96H96c-53 0-96-43-96-96v-320c0-53 43-96 96-96h465l135 136c37 36 85 56 136 56s99-20 136-56l136-136h464c53 0 96 43 96 96zm-325-569c10 24 5 52-14 70l-448 448c-12 13-29 19-45 19s-33-6-45-19L339 621c-19-18-24-46-14-70 10-23 33-39 59-39h256V64c0-35 29-64 64-64h256c35 0 64 29 64 64v448h256c26 0 49 16 59 39z](http://www.w3.org/2000/svg%22%3E%0A%09%09%20%20%20%20%3Cpath%20d=%22M1280%201344c0-35-29-64-64-64s-64%2029-64%2064%2029%2064%2064%2064%2064-29%2064-64zm256%200c0-35-29-64-64-64s-64%2029-64%2064%2029%2064%2064%2064%2064-29%2064-64zm128-224v320c0%2053-43%2096-96%2096H96c-53%200-96-43-96-96v-320c0-53%2043-96%2096-96h465l135%20136c37%2036%2085%2056%20136%2056s99-20%20136-56l136-136h464c53%200%2096%2043%2096%2096zm-325-569c10%2024%205%2052-14%2070l-448%20448c-12%2013-29%2019-45%2019s-33-6-45-19L339%20621c-19-18-24-46-14-70%2010-23%2033-39%2059-39h256V64c0-35%2029-64%2064-64h256c35%200%2064%2029%2064%2064v448h256c26%200%2049%2016%2059%2039z)"/>%0A%09%09</svg>)