[BUG] Every sync method results in SyncEncryptionNoKeyError

[Improver2000]

f this is mainly a sync/data integrity problem, please use the Sync / Data Issue template for faster triage.

💻 Platform

• Desktop (Linux - Arch/Hyprland/Niri/Other)
• Desktop (macOS)
• Desktop (Windows)
• Mobile (Android)
• Mobile (iOS)

🧭 Affected Area

• Sync / data consistency
• UI / interaction
• Projects / areas / sections
• Search / filter
• Settings / preferences
• Notifications / reminders
• Recurrence / calendar
• Attachments
• Audio / transcription
• Other

ℹ️ Environment

• App Version:
  1.2.6
• Install Channel:
  Play Store
• OS Version:
  Android 14
• Device:
  Samsung A52

🚨 Impact

• Blocks core workflow
• Data loss or data mismatch
• Crash / freeze
• Visual issue only

📝 Description

DropBox Sync failed initially:

SyncEncryptionNoKeyError: This sync folder is encrypted. Enter the sync passphrase to continue.

I had similar issues with WebDAV alternatives.

/Update: and even with folder sync!

Encryption is correctly enabled and renewed already.

🔄 Steps to Reproduce (REQUIRED)

1. Every sync with DropBox/WebDAV/Folder
2. See error

🎯 Expected Behavior

Sync with DropBox/WebDAV/Folder

Additional

• deleting data on Dropbox doesn't help

[Improver2000]

PS: Encryption is sooo important - thanks for supporting it 👍👍👍

[dongdongbh]

Thanks for the report, and for the kind words on encryption.

What that message means on your phone: the app keeps a device-local flag that says "this sync location is encrypted and this device has no key for it". While the flag is set, the phone refuses every sync on every backend before it contacts the server at all. That is why Dropbox, WebDAV and a plain folder fail the same way, and why clearing the Dropbox folder changed nothing. The only exit today is Settings > Sync > Encryption > Unlock, and Unlock needs the encrypted document to still exist at the location the phone points to. Empty that location or switch backends and the phone is stuck. That is a bug on our side: a lock must not outlive the location it was set for. I am fixing it so that a manual Sync re-checks the real folder and clears a stale flag, and so that Unlock tells you when there is nothing left to unlock.

Until that ships, the way out is to give Unlock something to check: point the phone at a location that still holds the encrypted data, or sync once from the device that has encryption turned on so data.json.enc is back on Dropbox, then use Unlock on the phone with the current passphrase. If the passphrase was changed on another device, the new one is the one to enter.

Two things would help me confirm this is your case:

1. Which device turned encryption on, and was the passphrase changed on a device other than the phone?
2. A log from the phone: Settings > Diagnostics > Debug logging on, tap Sync now once, then Share log.

[dongdongbh]

Fixed on main in 7da422c, on both phone and desktop.

What changed: the "this location is encrypted and this device has no key" lock is now tied to the exact location it was found on. A different backend or an emptied location is checked instead of refused. A phone already stuck on 1.2.6 recovers with one tap on Sync now after updating: the app re-reads the location, and if it no longer holds encrypted data the sync simply runs. Unlock at a location that holds no encrypted data now clears the stale lock and tells you encryption is off on this device, instead of failing.

It will be in the next release. Once you have it, tap Sync now on the phone and let me know here whether it syncs; if it still asks for a passphrase, that means the location really does hold encrypted files from another device, and the passphrase from that device unlocks it.