Issues with Cloud Sync #57

New issue

Closed

opened 2026-01-20 22:24:16 +00:00 by f_g · 0 comments

f_g commented

2026-01-20 22:24:16 +00:00

(Migrated from codeberg.org)

Description

UI not immediately updated.
Unable to enter data for a backup / cloud sync via NextCloud / WebDAV.
Right to left editing issue.

Steps to Reproduce

Go to Settings -> Data & Backup.
Tap S3 Compatible Storage.
Type in some data to a garage deployment.
Tap Test --> Test fails with an Unknown error.
Log of garage shows:
2026-01-20T21:38:54.430021Z INFO garage_api_common::generic_server: [::ffff:HEREISMYIPV4]:36356 (key HEREISTHEKEYTHATGOTASSIGNED HEAD /holos-backups/ 2026-01-20T21:38:54.430710Z INFO garage_api_common::generic_server: Response: error 400 Bad Request, Authorization header malformed, unexpected scope: 20260120/us-east-1/s3/aws4_request
I have set the s3_region for this bucket not to us-east-1 what holos seems to expect (but to garage instead). To my understanding from the garage documentation the client should automatically be redirected to the region set up in garage. Apparently holos does not support to be redirected.
If I set s3_region to us-east-1 holos is able to connect.
Tap Save. Tap Close.
Notice > to the right of S3 Compatible Storage was NOT replaced by blue check mark.
Tap NextCloud / WebDAV.
Unable to enter data in these fields. Maybe it is not yet enabled? There is text at the top of this screen Cloud sync is coming in a future update.
Tap Close.
Tap back.
Tap Data & Backup.
Notice > to the right of S3 Compatible Storage was now replaced by blue check mark.
Tap S3 Compatible Storage.
Strange editing going on in input field for Endpoint URL. Again some right to left issue.

Expected Behavior

Blue checkmak should be shown as soon as (vaild) data was saved. It is possible to save data with which holos is unable to connect.
It should be possible to set up NextCloud / WebDAV.
Editing in input fields of S3 Compatible Storage should be left to right.
Suggestion (might actually already be like this, but unable to confirm): It should be possible to set up NextCloud / WebDAV and S3 Compatible Storage at the same time. If both at the same time is not possible there should be a hint about it when trying to set up the second one.

Actual Behavior

See Steps to Reproduce.

(Backups to garage actually fail. I have yet to figure out if this is an issue with my garage setup or holos. The message garage logs is 2026-01-20T22:16:31.900840Z INFO garage_api_common::generic_server: Response: error 400 Bad Request, Invalid digest: Failed to validate checksum for algorithm Crc32: calculated Some(Crc32([53, 86, 46, 105])), expected Crc32([0, 0, 0, 0]). Holos correctly logs that the upload failed with error 400.)

Screenshots / Logs

Input field appear to be disabled / grayed out:

Environment

App version: beta-16

## Description 1. UI not immediately updated. 2. Unable to enter data for a backup / cloud sync via NextCloud / WebDAV. 3. Right to left editing issue. ## Steps to Reproduce 1. Go to `Settings` -> `Data & Backup`. 2. Tap `S3 Compatible Storage`. 3. Type in some data to a [garage](https://garagehq.deuxfleurs.fr/) deployment. 4. Tap `Test` --> Test fails with an `Unknown error`. Log of garage shows: `2026-01-20T21:38:54.430021Z INFO garage_api_common::generic_server: [::ffff:HEREISMYIPV4]:36356 (key HEREISTHEKEYTHATGOTASSIGNED HEAD /holos-backups/ 2026-01-20T21:38:54.430710Z INFO garage_api_common::generic_server: Response: error 400 Bad Request, Authorization header malformed, unexpected scope: 20260120/us-east-1/s3/aws4_request` I have set the s3_region for this bucket not to `us-east-1` what holos seems to expect (but to `garage` instead). To my understanding from the [garage documentation](https://garagehq.deuxfleurs.fr/documentation/connect/#generic-instructions) the client should automatically be redirected to the region set up in garage. Apparently holos does not support to be redirected. If I set s3_region to us-east-1 holos is able to connect. 5. Tap `Save`. Tap `Close`. 5. Notice `>` to the right of `S3 Compatible Storage` was NOT replaced by blue check mark. 5. Tap `NextCloud / WebDAV`. 6. Unable to enter data in these fields. Maybe it is not yet enabled? There is text at the top of this screen `Cloud sync is coming in a future update.` 7. Tap `Close`. 8. Tap back. 9. Tap `Data & Backup`. 10. Notice `>` to the right of `S3 Compatible Storage` was now replaced by blue check mark. 11. Tap `S3 Compatible Storage`. 12. Strange editing going on in input field for `Endpoint URL`. Again some right to left issue.  ## Expected Behavior 1. Blue checkmak should be shown as soon as (vaild) data was saved. It is possible to save data with which holos is unable to connect. 2. It should be possible to set up `NextCloud / WebDAV`. 3. Editing in input fields of `S3 Compatible Storage` should be left to right. 4. Suggestion (might actually already be like this, but unable to confirm): It should be possible to set up `NextCloud / WebDAV` and `S3 Compatible Storage` at the same time. If both at the same time is not possible there should be a hint about it when trying to set up the second one. ## Actual Behavior See `Steps to Reproduce`. (Backups to garage actually fail. I have yet to figure out if this is an issue with my garage setup or holos. The message garage logs is `2026-01-20T22:16:31.900840Z INFO garage_api_common::generic_server: Response: error 400 Bad Request, Invalid digest: Failed to validate checksum for algorithm Crc32: calculated Some(Crc32([53, 86, 46, 105])), expected Crc32([0, 0, 0, 0])`. Holos correctly logs that the upload failed with error 400.) ## Screenshots / Logs Input field appear to be disabled / grayed out: ![Screenshot_20260120_222352_Holos_s](/attachments/2afb28d0-2ca3-43b5-bf44-c76f7b5c6e20) ## Environment - **App version**: beta-16