Backblaze bucket does not get restored after connecting to the existing server #320

New Issue

Closed

opened 2023-08-29 13:48:03 +03:00 by inex · 1 comment

inex commented

2023-08-29 13:48:03 +03:00

Owner

Server provides information on bucket IDs, but app doesn't use it to recover the BackblazeBucket bucket object. As a side effect of this, backups cubit is not properly initialized and user can't see the backups key.

Steps to reproduce

Have an existing SelfPrivacy server, get any auth key for it. Backups must be initialized.
Use the fresh SelfPrivacy app to connect to this server
Open the "Backups" screen and click on "Encryption key"
Error happens

Expected behavior

The bucket object stored in app has all metadata of existing backblaze bucket. App can show the encryption key and, if requested, can re-initialize backups on the server.

Actual behavior

Fields of the objects are empty.

Note

We can't get existing appliction keys from backblaze, and we shouldn't create new ones unless really needed.

Server provides information on bucket IDs, but app doesn't use it to recover the `BackblazeBucket bucket` object. As a side effect of this, backups cubit is not properly initialized and user can't see the backups key. ## Steps to reproduce 1. Have an existing SelfPrivacy server, get any auth key for it. Backups must be initialized. 2. Use the fresh SelfPrivacy app to connect to this server 3. Open the "Backups" screen and click on "Encryption key" 4. Error happens ## Expected behavior The bucket object stored in app has all metadata of existing backblaze bucket. App can show the encryption key and, if requested, can re-initialize backups on the server. ## Actual behavior Fields of the objects are empty. ## Note We can't get existing appliction keys from backblaze, and we shouldn't create new ones unless really needed.