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

Coffee · 2024-06-14T17:30:21.612Z

personalizedrefriger:

Yes — it should work in Joplin 2.14. Be sure that you have an up-to-date backup before deleting anything though!

Thank you – I will try to be very careful and only use the plugin for the advanced analysis of details for the time being and not make any changes with it yet.

Coffee · 2024-06-14T17:39:55.682Z

I forked 2024-06-14 - A closer look at a new conflict

personalizedrefriger · 2024-06-14T18:02:42.728Z

Coffee:

Thank you – I will try to be very careful and only use the plugin for the advanced analysis of details for the time being and not make any changes with it yet.

I've just added documentation on how to show information for a specific note/notebook/resource from an ID. (Previously, documentation on this feature was missing).

Coffee · 2024-06-17T13:40:11.378Z

Coffee:

To limit the resulting risk to my data content, I only ran two apps this morning and deleted five apps completely. Since then, there seems to be no further uncontrollable increase in conflicts.

Even after running just two apps and waiting a very long time to see if they were fully synced, I still couldn't get the notes to stabilise.
That's why I decided to take another drastic step: I deleted my main profile in my Android app and started from scratch with the synchronisation from the Joplin cloud.
After more than 24 hours, no further synchronisation progress was visible in the Android app. However, the synchronisation status has since shown a fairly constant number of around 5500 attachments that have not been downloaded.
To get another reference value, I installed a Joplin app on an iPad for the first time.
After about 24 hours, synchronisation was also complete on the iPad. In contrast to the Android app, all attachments are displayed as downloaded and decrypted on the iPad in synchronisation status.

Coffee · 2024-06-17T13:51:36.573Z

Coffee:

To get another reference value, I installed a Joplin app on an iPad for the first time.

After about 24 hours, synchronisation was also complete on the iPad. In contrast to the Android app, all attachments are displayed as downloaded and decrypted on the iPad in synchronisation status.
I spent about an hour noting certain parameters from the synchronisation status and manually counted elements in the conflict folders on Android and iOS after synchronising all three apps several times to the same state. Some values are strikingly identical, others strikingly different

Coffee · 2024-06-17T13:59:45.003Z

Coffee:

noting certain parameters

Number of attachments = 7445

Android: 5464 not downloaded + 1980 downloaded and decrypted +    1 created locally  
iOS:        0 not downloaded + 7445 downloaded and decrypted +    0 locally created  
Windows:    0 not downloaded + 1698 downloaded and decrypted + 5747 created locally

Coffee · 2024-06-17T14:13:56.761Z

Coffee:

noting certain parameters

Conflicts:

Android:   1  
iOS:      94  
Windows: 642

Coffee · 2024-06-17T14:16:32.649Z

Coffee:

noting certain parameters

Conflicts (attachments) = 413

Android: 413  
iOS:     413  
Windows: 413

Coffee · 2024-06-17T14:22:30.994Z

laurent:

so you'd need to make sure synchronisation goes to completion on all of them

Is there anything I can do to ensure that the newly created profile in the Android app downloads all the attachments? I don't think so. I think that's a problem you'll have to find a solution for.

Coffee · 2024-06-17T14:35:24.936Z

Coffee:

you'll have to find a solution for

What I can contribute is a file of about 1.5 MB with error log data.
Since I found words in it that came from my confidential data, I don't want to make them public here.

Coffee · 2024-06-17T14:41:12.091Z

Coffee:

file of about 1.5 MB with error log data

The file starts with

06-15T20:47:20: JoplinServerApi: "TypeError: Network request failed
TypeError: Network request failed
    at anonymous (address at index.android.bundle:1:250949)
    at apply (native)
    at anonymous (address at index.android.bundle:1:219117)
    at _callTimer (address at index.android.bundle:1:218401)
    at callTimers (address at index.android.bundle:1:220192)
    at apply (native)
    at __callFunction (address at index.android.bundle:1:122367)
    at anonymous (address at index.android.bundle:1:120737)
    at __guard (address at index.android.bundle:1:121687)
    at callFunctionReturnFlushedQueue (address at index.android.bundle:1:120695)"
06-15T20:47:20: JoplinServerApi: "curl -v -X POST -H "X-API-AUTH: ******" -H "X-API-MIN-VERSION: 2.6.0" -H "Content-Type: application/json" -H "Content-Length: 71" --data '{"type":1,"clientType":2,"clientId":"725c0e857a244e5fa493c51281f6522b"}' 'https://api.joplincloud.com/api/locks'"
06-15T20:47:20: JoplinServerApi: "Code:", "undefined"

laurent · 2024-06-17T14:41:27.214Z

It should download all attachments by default. I'm not grasping the complexity of your particular case at the moment since there are many posts, but if you can narrow it down that may help. For example you have a specific image in desktop, and it doesn't appear in mobile, let's find out why.

Coffee · 2024-06-17T14:43:43.228Z

Coffee:

file of about 1.5 MB with error log data

The file ends with

06-03T18:43:05: JoplinServerApi: "curl -v -X GET -H "X-API-AUTH: ******" -H "X-API-MIN-VERSION: 2.6.0" 'https://api.joplincloud.com/api/items/root:/temp/timeCheck287026.txt:'"
06-03T12:40:15: Synchronizer: "Could not refresh lock - cancelling sync. Error was:", "Error: Lock has expired
Code: lockExpired
Error: Lock has expired
    at construct (native)
    at Wrapper (address at index.android.bundle:1:2619599)
    at construct (native)
    at _createSuperInternal (address at index.android.bundle:1:2618675)
    at call (native)
    at JoplinError (address at index.android.bundle:1:2619053)
    at ?anon_0_ (address at index.android.bundle:1:2912346)
    at next (native)
    at fulfilled (address at index.android.bundle:1:2907992)
    at tryCallOne (/root/react-native/ReactAndroid/hermes-engine/.cxx/MinSizeRel/5p1x2e66/arm64-v8a/lib/InternalBytecode/InternalBytecode.js:53:16)
    at anonymous (/root/react-native/ReactAndroid/hermes-engine/.cxx/MinSizeRel/5p1x2e66/arm64-v8a/lib/InternalBytecode/InternalBytecode.js:139:27)
    at apply (native)
    at anonymous (address at index.android.bundle:1:219452)
    at _callTimer (address at index.android.bundle:1:218401)
    at _callReactNativeMicrotasksPass (address at index.android.bundle:1:218565)
    at callReactNativeMicrotasks (address at index.android.bundle:1:220540)
    at __callReactNativeMicrotasks (address at index.android.bundle:1:121846)
    at anonymous (address at index.android.bundle:1:120939)
    at __guard (address at index.android.bundle:1:121687)
    at flushedQueue (address at index.android.bundle:1:120850)
    at invokeCallbackAndReturnFlushedQueue (address at index.android.bundle:1:120793)"

Coffee · 2024-06-17T14:49:06.513Z

Coffee:

06-03T18:43:05

When I read

06-03T18:43:05 and
06-15T20:47:20

as timestamps, this should mean that this data does not just refer to the newly created profile.

Coffee · 2024-06-17T14:54:31.538Z

laurent:

For example you have a specific image in desktop, and it doesn't appear in mobile, let's find out why.

In my opinion, there are many of them.
I will try to work out a new individual case.

Coffee · 2024-06-17T15:00:24.508Z

Coffee:

I will try to work out a new individual case.

My first attempt at such an individual case analysis on 14 June still used data from the now deleted Android profile. Would the form and content of the description be ok, or should I provide more or different information?

2024-06-14 - A closer look at a new conflict Support

Operating system Android Joplin version 2.14.9 Desktop version info Joplin 2.14.22 (prod, win32) Client-ID: c5213521ab8148f6a62f5f728496c793 Sync-Version: 3 Profil-Version: 46 Unterstützter Schlüsselbund: Ja Revision: e579eb9 Backup: 1.4.1 Conflict Resolution: 1.2.3 Sync target Joplin Cloud What issue do you have? This is forked from 2024-04-29 - Problems synchronising with the Android app and the Joplin Cloud - #25 by Coffee At around 5 p.m., I created a new note using the Windows a…

Coffee · 2024-06-17T16:02:06.314Z

Coffee:

I will try to work out a new individual case.

2024-06-17 - An Android download problem in more detail Support

Operating system Android Joplin version 2.14.9 Desktop version info Joplin 2.14.22 (prod, win32) Client-ID: ... Sync-Version: 3 Profil-Version: 46 Unterstützter Schlüsselbund: Ja Revision: e579eb9 Backup: 1.4.1 Conflict Resolution: 1.2.3 Joplin debug tool: 0.2.0 Sync target Joplin Cloud What issue do you have? In this example, it is most likely a case in which I documented an article from the Spiegel portal in a new note on my Android Samung S23. I probably performed 2 or 3 saving op…

Coffee · 2024-06-17T16:42:00.232Z

laurent:

For example you have a specific image in desktop, and it doesn't appear in mobile, ...

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

laurent:

let's find out why

What do you think?

2024-06-17 - An Android download problem in more detail Support

Operating system Android Joplin version 2.14.9 Desktop version info Joplin 2.14.22 (prod, win32) Client-ID: ... Sync-Version: 3 Profil-Version: 46 Unterstützter Schlüsselbund: Ja Revision: e579eb9 Backup: 1.4.1 Conflict Resolution: 1.2.3 Joplin debug tool: 0.2.0 Sync target Joplin Cloud What issue do you have? This is forked from 2024-04-29 - Problems synchronising with the Android app and the Joplin Cloud - #35 by laurent In this example, it is most likely a case in which I documen…

Coffee · 2024-06-23T15:27:57.906Z

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.

Coffee · 2024-06-23T15:29:20.017Z

Coffee:

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.