Joplin Android sync problem and error

[_Ben]

Operating system

Android

Joplin version

3.1.8

Sync target

Dropbox

What issue do you have?

Hi

I’ve been successfully using Joplin running the desktop version Joplin 2.14.20 (prod, win32) on a couple of machines alongside the Chen fork (background sync) on Android, Joplin-v2.10.6.

This was all running well with no issues. But wanting to run newer plugins and not get left behind, I decided to upgrade my desktop machines to the latest version – this went smoothly – and I also upgraded Android to the latest official version. This is where I have a sync problem. The app only syncs about 600 of about 6000 notes, I think, and then I get a "RangeError" sync error - screenshot attached.

Note that, FWIW, I was careful when upgrading an ensured no other instances were running when I upgraded each machine (desktop first then Android). I’ve tried the latest Android version as well as rolling back to 3.0.7 but it made no difference. It’s a bit of mystery because, like I say, everything was working fine previously with the older version, and nothing has changed with regard to my notes.

I’d really appreciate some help on how to solve this and successfully sync Android, as before. Big thanks in advance.

Ben

Edit: I just deleted the apparently offending file (just a small PDF so it's odd) from the sync target in the hope that'd solve it. But I'm still getting the error when I try to sync again.

Screenshots

[_Ben]

Well, it looks like I've managed to fix this myself

I'd already deleted the offending file from Dropbox as mentioned above, but I went further and deleted any reference to it my desktop notebooks, emptied the trash and sync-ed (I didn't touch the local resources folder as I think that may have confused things further, though did consider it as a potential last resort!).

Now the Android app appears to have skipped the issue and has completed syncing all of my notes, thankfully.

It's a strange one though as it's just a small PDF file of little consequence; I don't understand how it could cause an out of memory error. Seems like a bug to me.

Anyway, just thought I'd follow-up in case anyone else runs across a similar issue - I couldn't find much about this specific error message online.

Cheers
Ben