2024-04-29 - Problems synchronising with the Android app and the Joplin Cloud

I finished my detailed report today, 2024-06-17 at 18:40.

What do you think?

2024-06-23 - some conflicts resolved carefully

Since I uninstalled all the instances of Joplin apps that I didn't really need and deleted my main profile in my Android app and then synchronised it fresh from the Joplin cloud, I haven't felt any uncontrollable increase in the number of conflicts in the data of my main profile.

Today I dared to carefully resolve the first conflicts. To do this, I used the
Conflict Resolution 1.2.3
plug-in in my Windows app.

The figures in the synchronisation status have improved accordingly. The improved values and notes have been synchronised to the Android app and the iOS app.

In doing so, I encountered a problem in the iOS app that prevented me from checking the result of one of the corrections in iOS.

I forked 2024-06-23-ios-content-of-a-subfolder-not-accessible to describe it.

I may have the same problem. Sync is super fast on Desktop but on Android app, it's super slow.

I am running a dockerised Joplin server.

2024-06-27 - Just a coincidence?

After a few days without any problems with new conflicts and even being able to solve a few conflicts manually, I had a series of "attachment conflicts" again today for the first time. I find it strange that these conflicts occurred immediately after I had created a new published note.

Is that just a coincidence – or is there a connection?

Screenshot 2024-06-27 194824

The number of conflicts in my Android app has risen again to 194, after I manually cleaned it up from 790 to 0 on 2024-06-16.
Since 2024-06-13, I have been recording the sync status figures for my Android app and my Windows app on a daily basis, and since 2024-06-16, I have also been doing so for my iPad app.
The numbers there raise further questions. For example, each app shows a different number of notes.
I will continue to create and store a JEX export of my data from my Windows app on a weekly basis.
I assume that a first V3 of the Joplin app will be released soon.
I hope that my data will remain clean enough until then, without me having to spend more time on detailed analyses.
The Note Info plugin for Android should also be available by then.
We'll see how the sync status figures develop and whether it will be possible to get my data clean with V3.
In the meantime, I have also found out that certain folders and notes that are shared between Joplin Cloud IDs are unfortunately not shared, contrary to expectations.
If I have to make this discovery with V3 as well, I will create a new post on a new topic of problems with shared folders and notes.

Today the updates to V3 for Windows and Android have arrived
Joplin 3.0.12 (prod, win32)
Joplin 3.0.7 (prod, android)
iPAD still on 12.14.8
On Android, I have taken advantage of the new option since 3.0 to install a first plugin:
Joplin debug tool: 0.2.0

I have derived a feature request from this

My 2024-07-06 - 3:00 pm fork of this is:

Now I am starting my first deep dive using your plugin and questions about details come to my mind.

What is the meaning of
encryption_applied = 0

grafik

If encryption_applied is 1, the item is waiting to be decrypted by Joplin. For example, if end-to-end encryption is enabled, items that have been just downloaded from the sync target might have encryption_applied set to 1. After being processed by Joplin's DecryptionWorker, these items should have encryption_applied=0.

encryption_applied should refer to the local state of the item, not the remote state.

1 Like

@personalizedrefriger

What is the meaning of

  1. updated_time
  2. user_updated_time

user_updated_time is the "last updated" time that you can manually set in the note property. updated_time is the effective "last updated" time.

By the way we document all this, so if you are wondering about any property, it's all in the help page: Joplin Data API | Joplin (the search function is also useful to search for a specific property)

1 Like

Thanks for this recommendation

What is the purpose of being able to change the values for user_updated_time and user_created_time manually?

One obvious use case is when importing notes from another app. Internally we want the created_time property to be the real time when the note was imported (as it is used for sync purposes). However user_created_time will be set to the time when the note was created in the other note taking app. That allows preserving timestamps basically.

In the forum you'll also find some users who want to change the timestamp because they accidentally modified the note for example.

1 Like

2024-07-06 - 21:28 - Windows Update - Joplin 3.0.13 (prod, win32)

Now I have
Joplin 3.0.13 (prod, win32)
Joplin 3.0.7 (prod, android)
Joplin 12.14.8 on iPAD

My 2024-07-06 - 10:30 pm fork of this is:

My 2024-07-07 - 19:40 pm fork of this is:

Even with Joplin 3.0.8 (prod, android) I still have 5501 attachments that have not been downloaded.
I suspect that the Android app currently only downloads individual attachments when I open a note whose attachments have not yet been downloaded.
Who needs to do what to ensure that a future version of Joplin on Android really downloads all attachments at once?

With Joplin 3.0.8 (prod, android) I still have 5458 attachments that have not been downloaded.
I suspect that the Android app currently only downloads individual attachments when I open a note whose attachments have not yet been downloaded.
Who needs to do what to ensure that a future version of Joplin on Android really downloads all attachments at once, @laurent ?