actualbudget / actualbudget/actual

[Bug]: cannot sync local after enabling encryption on remote

Offen
#3,620 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
user interface
Vorherrschende Sprache
TypeScript
Sterne
28.8k
Forks
3k
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
65

Beschreibung

### Verified issue does not already exist?

- [X] I have searched and found no existing issue
- [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

### What happened?

I enabled encryption remotely. Going back to the local I got the expected

> Syncing has been reset on this cloud file
You need to revert it to continue syncing. Any unsynced data will be lost. If you like, you can instead upload this file to be the latest version. [Learn more](https://actualbudget.org/docs/getting-started/sync/#debugging-sync-issues)

Clicking "revert" shows me the "downloading" screen and takes me to the file list.

Clicking on the file opens it, with the ⚠️ icon next to the sync button and that same toast warning.

Both remote and local are on 24.10.1

Maybe relevant: when I enabled encryption on the remote, the remote was on 24.10.1 and local was on 24.10.0. After encrypting on the remote and [attempting] reverting on the local, in the local file list view hovering over the file's 🔑 icon showed a "this file is encrypted and you don't have the key" title.

### Where are you hosting Actual?

Fly.io

### What browsers are you seeing the problem on?

_No response_

### Operating System

Mac OSX

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by reproducing with two Actual clients around 24.10.0/24.10.1: enable encryption on the remote, then use the local file list Revert flow. Read the sync reset, encryption key, and file list warning paths that show the toast and key icon. Done means reverting after remote encryption downloads/opens the file without the repeated warning or missing-key state.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
typescript
Bereich
data, security
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
28/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.