I was using the latest portable build on Windows 10, and it worked well most of the time. However, yesterday, I noticed that my local notes were outdated. I tried syncing, but it failed.
So, I decided to delete the local data and re-download it. Unfortunately, the synchronization took a long time to complete. It would fetch up to 1,000 items but rarely create new local items, and errors kept occurring. I had to restart the sync multiple times, but the errors persisted.
I even created a new profile to download from OneDrive and tried changing the network proxy, but nothing worked. It took several hours without a note created.
Finally, I switched to version 3.2.5, and the synchronization completed without any errors.
Just for your information.
Do you have a record of the error messages you experienced, or have any error logs from when you experienced the sync errors?
I happened to take some screenshots while fetching notes from OneDrive with latest build on Pixel 6.
They all seemed similar on latest Windows, Android as well as IOS, which I just started to use yesterday, I have been using others almost half a year.
"What I am trying to say is when turned to 3.2.5 Windows build, I succeeded in downloading up to 2000 notes and 3000+ attachments without an error.*
Are you saying that on all 3 of your devices you upgraded and had issues with the sync, and then all 3 devices you downgraded to an older version and it is working again? Or do you still have any devices on the latest version in a broken state?
If you still have any devices in a broken state, please export the full log, zip it and post in this thread.
1 Like
Not exactly.
On android or iOS, I managed to fetch and create local items from OneDrive throughout multiple tries.
But, on the Windows I can't. With the latest build, the App keeps fetching items until errors appear. Just similar to my previous screenshots. I keep manually do the synchronization, errors come up, I Keep... Several hours passed, no new local items were created.
When I changed to 3.2.5, it automatically finishes syncing, once at a time. It took about 1 hour to fetch and create all together more than 6000 items
So your pixel is currently on the latest version? In that case a suitable log is still available. It's difficult to tell what the issue is without the log, as only a snippet of the error message is available on the screenshots
This is my major PC. It seems that every single synchronisation fetches all items. I am uploading the zipped log, please help take a look.
error occured several mintues ago @mrjo118
There is actually no new notres on Onedrive, but the synchroinasiton tecthed most of the items untill there is an error.
Created local items: 12.
Fetched items: 4350/4362.
Completed: 2025/01/24 19:02 (1166s)
Last error: Error: On file 3ab54aef1c5e1618a3df4b11b5ede5c7.md: Sharepoint Online body,html { font: 18px/normal "Segoe UI",Arial,Helvetica,Sans-Seri
log.zip (3.5 MB)
Joplin 3.2.12 (prod, win32)
Client ID: 030fb9c047f64ec6a1018a21c25f1224
Sync Version: 3
Profile Version: 47
Keychain Supported: No
Revision: d6f1ca4
Github Alerts: 1.0.5
Journal: 1.2.0
Markmap: 1.7.0
Rich Markdown: 0.15.1
Thanks for this. So basically the OneDrive api is returning a html page sometimes, instead of a json response. If I put the response in a html file, the output looks like this:
Aside from the response included in the error message and log, the important part of the error is this:
Unexpected token '<', "<!DOCTYPE "... is not valid JSON
at JSON.parse ()
at OneDriveApi.exec (C:\Users\mzx\AppData\Local\Temp\2rFszUCMYon6udzD2dzGVU1Wxbc\resources\app.asar\node_modules@joplin\lib\onedrive-api.js:321:42)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async OneDriveApi.execText (C:\Users\mzx\AppData\Local\Temp\2rFszUCMYon6udzD2dzGVU1Wxbc\resources\app.asar\node_modules@joplin\lib\onedrive-api.js:425:26)
at async FileApiDriverOneDrive.get (C:\Users\mzx\AppData\Local\Temp\2rFszUCMYon6udzD2dzGVU1Wxbc\resources\app.asar\node_modules@joplin\lib\file-api-driver-onedrive.js:113:21)
at async tryAndRepeat (C:\Users\mzx\AppData\Local\Temp\2rFszUCMYon6udzD2dzGVU1Wxbc\resources\app.asar\node_modules@joplin\lib\file-api.js:52:28)
at async Synchronizer.apiCall (C:\Users\mzx\AppData\Local\Temp\2rFszUCMYon6udzD2dzGVU1Wxbc\resources\app.asar\node_modules@joplin\lib\Synchronizer.js:336:28)
From searching the log for instances of the resource it failed on, it looks like the resource was able to download correctly shortly afterwards, so it looks to be an intermittent issue when downloading files with OneDrive api. But I've got no idea why this would suddenly start happening in the latest version of Joplin on multiple devices, yet it worked fine when downgrading. I can't find any recent code changes in Joplin regarding the OneDrive sync.
1 Like
Thank you for the efforts. I have don't know much about these code stuffs. Maybe something happened with OneDrive. For now, let it be.
Thank YOU