Some items cannot be decrypted

Operating system

Windows

Joplin version

3.5.13

Desktop version info

Joplin 3.5.13 (prod, win32)

Device: win32, Intel(R) Core(TM) i5-14600
Client ID: 3145ffa5fbef472693ad5fb37509e2a4
Sync Version: 3
Profile Version: 49
Keychain Supported: Yes
Alternative instance ID: -

Revision: 0c1511f

Backup: 1.5.1
Freehand Drawing: 4.2.0

Sync target

Joplin Cloud

What issue do you have?

Joplin is installed on 2 desktops, 2 laptops and an Android phone.

All of a sudden I'm getting the "Some Items Cannot Be Decrypted" banner on all Windows devices (Android device seems okay). I've clicked on "retry" multiple times and re-encrypted and resynced - no joy. Screenshot and log file uploaded.

Screenshots

Log file

syncReport-1776265912715.csv (18.8 KB)log.txt (38.1 KB)log.txt (46.5 KB)

I think this is likely caused by an issue with the encryption on Android, see my comment here https://github.com/laurent22/joplin/issues/14975#issuecomment-4246731347

I suspect based on the types and frequencies of the items which could not be decrypted, that most of those items are from the default welcome notebook (especially if you deleted it) when you did initial device setup on Android.

The good news is we have a known fix for the encryption issue, so I expect this will be fixed in Joplin 3.6 when it is released. Regardless, you will still need to clean up these items on the server though (by deleting the item with the matching id), in order to remove the sync errors. Be sure to make a jex backup on a known good client (seems like this is the Android one, as this has no errors) before deleting anything though.

Thank you. Are you saying I have to open every message, click on the information icon, and look for matching id's? Surely there must be a faster way, no?

What information icon do you mean? All of the ids are in the screenshot which you posted

But how do I find the associated note to delete it?

Oh you're using Joplin Cloud. I'm not sure you can remove those items yourself, as they need to be removed from the server. I think you will need @laurent to assist

So my next step is....?