Android - sync not working - changes not updating on desktop, no error message

Android version 1.0.331

Changes to notes, or new notes added on Android are not being synced to other devices. This is recent, it might be as of the latest update.

Changes done on desktop are being synced to Android.

What an I missing?
syncReport-1591784889799.txt (542.2 KB)

What sync method are you using? Do you have encryption enabled?

No encryption. I’m just pressing the ‘sync’ button, which had always worked before. Permissions are fine, too. I sync to One Drive.Screenshot_20200610-132038|281x500

out of curiosity, have you tried to see if another sync method works ? like dropbox ?

No, because I don’t want to try switching to another service, which takes ages (I’ve got a lot of notes and it can take forever) and risk finding the problem persists. Are you saying one drive is inherently toxic and is best avoided? Maybe I should switch to Next Cloud like everyone else in this forum.

The plot, however, thickens. It seems it is not the Android app that is at fault: any changes made there sync fine to the iPad version. It is the windows version that is refusing to update any changes.

I’m using Joplin Windows version:
Joplin 1.0.216 (prod, win32)

Client ID: f36898bba6e94718bdaac85f1cbb3862
Sync Version: 1
Profile Version: 29

Revision: 4eb680d6 (master)

On Synchronization/Advanced Settings “Failsafe” is set to ON. Which, as far as I can tell, has always been the case.

Can it be something is amiss on the latest Windows version of Joplin?

No, because I don’t want to try switching to another service, which takes ages

I wasn’t suggesting you switch. It was a debugging effort to see if you can get something else working. I had no issues with dropbox and I’m a new user.

So in your first message you said changes from desktop are synced to android but now it turns out changes from Android do not appear on your desktop?
What about iPad - does it see changes from desktop/android? And do other devices see changes from iPad?

Can you open dev tools on your desktop, run sync and check for any errors in console?

Thanks for the replies.
Yes, iPad also sees changes done on Android. Haven’t checked whether it is seeing changes made on Desktop.
I’ve tried switching “Fail-safe” to “Off” on Windows desktop, to check if it made a difference (you never know), it doesn’t. The changes made on Android are still not being synced to Windows desktop.
Devtools: I’ve tried creating the flags.txt file as per the online debugging docs, but I can’t see any console tab.
What do I need to do to run devtools on Windows?

Isn't Help - Toggle Development Tools not working for you?

Anyway, let's try something different.

Can you make a change to some note (or create a new one) on Android, sync and make a screenshot of that note's properties on Android.
And then find that note in your OneDrive and paste here its metadata. Or better yet find all files that contain that note's ID (there may be more than one) and share the metadata.

And if you changed an existing note that is visilble on desktop then also sync and share that note's properties.

Devtools is now working. I enclose a copy paste of the console section.
Thanks for the tip on Android, I’ll try that out next.

main-html.js:59 Environment: prod
C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • If you’re updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
  • Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteEditor), Connect(NoteListComponent), Connect(RootComponent), Connect(SideBarComponent), Provider
printWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(HeaderComponent), Connect(MainScreenComponent), Connect(NavigatorComponent), Connect(NoteEditor), Connect(NoteListComponent), Connect(RootComponent), Connect(SideBarComponent)
printWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/fence.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/sanitize_html.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/checkbox.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/mermaid.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/markdownItAnchor.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/markdownItTocDoneRight.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/JoplinServerApi.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/NoteEditor.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/TinyMCE.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/types.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/resourceHandling.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useScroll.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/contextMenu.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/taboverride.min.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/AceEditor.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/index.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useListIdent.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/Toolbar.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/index.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/types.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/MultiNoteActions.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/NoteToolbar.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/index.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useSearchMarkers.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useNoteSearchBar.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useMessageHandler.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useWindowCommandHandler.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useDropHandler.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useMarkupToHtml.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/useFormNote.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/AsyncActionQueue.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/usePrevious.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/index.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/performance-now.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/NoteContentPropertiesDialog.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/ShareNoteDialog.js.map
DevTools failed to parse SourceMap: file:///C:/Program%20Files/Joplin/resources/app.asar/ResourceScreen.js.map
C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • If you’re updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
  • Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(NoteTextViewerComponent), Connect(NoteToolbar), Connect(ToolbarComponent), ReactAce
printWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11680
flushRenderPhaseStrictModeWarningsInDEV @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
dispatchAction @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:15816
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:70
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
initNoteState @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:43
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:137
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
loadNote @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:129
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:143
commitHookEffectList @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:19986
commitPassiveHookEffects @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:20016
callCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:347
invokeGuardedCallbackDev @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:397
invokeGuardedCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:454
flushPassiveEffectsImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22868
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushPassiveEffects @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22841
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22419
scheduler_flushTaskAtPriority_Normal @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:436
flushTask @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:482
flushWork @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:607
performWorkUntilDeadline @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:231
C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Connect(NoteTextViewerComponent), Connect(NoteToolbar), Connect(ToolbarComponent)
printWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11686
flushRenderPhaseStrictModeWarningsInDEV @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
dispatchAction @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:15816
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:70
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
initNoteState @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:43
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:137
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
fulfilled @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
loadNote @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:129
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:143
commitHookEffectList @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:19986
commitPassiveHookEffects @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:20016
callCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:347
invokeGuardedCallbackDev @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:397
invokeGuardedCallback @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:454
flushPassiveEffectsImpl @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22868
unstable_runWithPriority @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushPassiveEffects @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22841
(anonymous) @ C:\Program Files\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22419
scheduler_flushTaskAtPriority_Normal @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:436
flushTask @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:482
flushWork @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:607
performWorkUntilDeadline @ C:\Program Files\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:231
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Program Files\Joplin\resources\app.asar\lib\logger.js:126 09:55:16 Starting Clipper server on port 41184
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Program Files\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]

Okay, I’ve created a new note. Here’s the Android screenshot of the properties.

And here’s the metadata (or what I suppose is the metadata of the latest three files) in the OneDrive folder:

Test

This is a test

id: caf74ecc12e34f18b7329bbac8055a31
parent_id: ebaac8bf5fc8492b9a2d68157db38999
created_time: 2020-06-10T16:55:03.573Z
updated_time: 2020-06-11T08:59:56.778Z
is_conflict: 0
latitude: 0.00000000
longitude: 0.00000000
altitude: 0.0000
author:
source_url:
is_todo: 0
todo_due: 0
todo_completed: 0
source: joplin
source_application: net.cozic.joplin-mobile
application_data:
order: 1591808103572
user_created_time: 2020-06-10T16:55:03.573Z
user_updated_time: 2020-06-11T08:59:56.778Z
encryption_cipher_text:
encryption_applied: 0
markup_language: 1
is_shared: 0
type_: 1

id: 8c969ab7f9bd4a94add51b8ec088fdfe
parent_id: 277255fc3af84d36871d4a8d4e826acf
item_type: 1
item_id: caf74ecc12e34f18b7329bbac8055a31
item_updated_time: 1591865996778
title_diff: “@@ -1,2 +1,4 @@\n-Kk\n+Test\n”
body_diff: “@@ -1,5 +1,14 @@\n-Peich\n+This is a test\n”
metadata_diff: {“new”:{},“deleted”:[]}
encryption_cipher_text:
encryption_applied: 0
updated_time: 2020-06-11T09:00:10.836Z
created_time: 2020-06-11T09:00:10.836Z
type_: 13

id: 254a8d12e51a4a6fb64978e6e1abce01
parent_id:
item_type: 1
item_id: a34c9686fea94cb8aa7f54902799fa57
item_updated_time: 1591866269051
title_diff: “@@ -0,0 +1,4 @@\n+Test\n”
body_diff: “@@ -0,0 +1,42 @@\n+%5BTest%5D(:/caf74ecc12e34f18b7329bbac8055a31)\n”
metadata_diff: {“new”:{“markup_language”:1,“source_application”:“net.cozic.joplin-mobile”,“source”:“joplin”,“todo_completed”:0,“is_todo”:0,“altitude”:“0.0000”,“longitude”:“0.00000000”,“id”:“a34c9686fea94cb8aa7f54902799fa57”,“is_shared”:0,“application_data”:"",“latitude”:“0.00000000”,“todo_due”:0,“author”:"",“parent_id”:“ebaac8bf5fc8492b9a2d68157db38999”,“order”:1591866265047,“source_url”:""},“deleted”:[]}
encryption_cipher_text:
encryption_applied: 0
updated_time: 2020-06-11T09:11:50.830Z
created_time: 2020-06-11T09:11:50.830Z
type_: 13

I’m afraid it does not tell much. The logging around synchronization could definitely be better.

I almost with I had the same issue so that I could investigate but I’m not using Jolplin on Android much these days - I’m at home all the time anyway.

Thanks again for the reply.

However, I’m in a bit of a problem here. I quit Evernote because of unreliable results, dodgy support and random nuking of note formatting with each update. I’ve never had a problem with Joplin in the year since I started using it, but now I’m in a serious bind. Is no one else having issues with the desktop version? Would uninstalling and reinstalling (with the resultant endless sync over the Internet) help?

Can you try to narrow down the problem?

  • Create one note on Android
  • Sync
  • Export the complete log in Android
  • Sync on desktop
  • Please tell us what happens at this point - is the note synced or not?
  • Export the complete log on desktop (the log.txt file in the profile directory. The console doesn’t provide any info for sync)

I had a similar problem and I tried a lot to find a way to reproduce this error but I couldn't find a way to do so. I think this issue is related to: Sync with OneDrive fails · Issue #3237 · laurent22/joplin · GitHub. Also I think the issue is not related to one specific platform but it is something going wrong during the sync process with multiple devices. In my case I had no synchronization problems between linux and android using OneDrive. But yesterday I installed joplin on a Windows machine and in this case some notes just have been ignored. Out of curiosity I then tried to install joplin on another (virtual) Linux device and it had the same problem as on Windows. I solved the problem with the following steps:

  1. Exported all my notebooks to a .jex File (luckily I had one machine with all notes)
  2. Deleted the joplin-desktop folder
  3. Cleared all data from android version
  4. Deleted the joplin folder in onedrive
  5. Imported the .jex File again to Joplin and logged in to Onedrive

Since then I didn't have any problems (but it was just yesterday so maybe the problems come back). The disadvantage is obviously that all notes had to been uploaded again. Unfortunately I forgot to make a debug log :frowning:

Thanks for the reply. I’ve created a new note on Android, synced, and exported the debug report (is this what you meant? I can’t find an option to export the log in Android).

I then synced on desktop and the note, as usual, is not there. It has not been synced to desktop.

I enclose the Android debug report, and the desktop log. Thanks again.

syncReport-1592056987102.txt (599.7 KB)
log.txt (2.0 MB)

Thanks for that! I’ll try it out if nothing else works. It would take ages to upload all my stuff again, and I’d rather avoid that if possible.

The last error for Android is Network request failed without more information, so it’s some network issue we can’t help much with. If you search for “onedrive” on the GitHub repo or here you’ll find various issues and how users fixed them.

@lumogas On your windows version you also had recently a lot of Errors saying: Error: The maximum request length supported is 4MB in the . You can solve this error by updating your Joplin version as this limitation has been fixed in v1.0.218. However I don't think that this fixes your issue you have been asked for :cry:.

…solved! Updating to the latest Windows version fixed the problem. Everything syncs again. I can save notes in Windows, and they appear on Android and iOS, I can save on Android and they appear on Windows and iOS, I can…
…you get the idea.
Thanks for the replies, chaps. Johnny, thanks for the tip on the Windows update. Laurent, I am flattered that you addressed tiny little me with my problem. I will nevertheless look at the Github pages in case this happens again.
What a relief! I can stop doing searches on “Importing notes from Joplin to Evernote” now. Life is good.

1 Like