actualbudget / actualbudget/actual

[Bug]: Internal error when trying to sync accounts with GoCardless when restoring from a backup

Ouverte
#4,742 5 commentaires 3 réactions 0 personnes assignées Voir sur GitHub
bank sync good first issue help wanted
Langage dominant
TypeScript
Étoiles
28.7k
Forks
3k
Merge moyen
2 j 11 h
PR mergées (30 j)
65

Description

### Verified issue does not already exist?

- [x] I have searched and found no existing issue

### What happened?

When restoring a backup it does not seem like the GoCardless `Secret Id` and `Secret Key` are restored.
If a user tries to sync the bank accounts after restoring a backup the message "An internal error has occured" appears.

Since there is no indication that the secrets are not restored it is highly confusing for a user to repair the problem.
I was thinking I had to set up a whole new instance and backfill all changes because I could not get it working again and there was no "Repair GoCardless sync" button or something.

To fix this one has to go to "Add an Account", "Set-up GoCardless for bank-sync" and add the secrets there (again). After that syncing works again.

### How can we reproduce the issue?

1. Set up an Actual instance with a bank account that is synced with GoCardless
2. Create a Backup of that instance ("Export data")
3. Delete everything; Set up a new instance.
4. Import the backup into that instance
5. Click "Sync" on the bank account that should be connected with GoCardless
6. See "internal error" occuring

### Where are you hosting Actual?

Other

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

Chrome, Firefox

### Operating System

Linux

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.