Torsten Grote

> Alternately allow se;f signed certs like DAV5x does Seedvault should already allow you to use self-signed certs: https://github.com/seedvault-app/seedvault/commit/5f6576a16386703c590bd3aa80f14891a297cf0d What we can't easily do is cleartext/unencrypted comms.

did you add the self signed cert to the system cert store?

This would mean that if users have both app and file (aka storage) backup on then, they'd get two notifications each time.

this is targeting `android14`, but we are on `android15`, so this needs a bit of work with weblate to straighten this out. @mikeNG knows how.

need to test if this is still an issue after the refactoring from https://github.com/seedvault-app/seedvault/pull/647

Some info how the system is preparing app data for backup: * creating the tarball for app data [happens in native code](https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/app/backup/FullBackup.java;l=159;drc=266063752d997701325cdfbf1f5f1af20ef3e45a). * tarballs include an app manifest [written by...

> So two backup runs against the same data may produce different tarballs which is bad for deduplication. Sorting the files there may help. Haven't noticed non-determinism even though files...

The research outcome is now documented at https://github.com/seedvault-app/seedvault/tree/android15/doc and was implemented in #750

> I suspect a Seedvault bug. Would you please be so nice and export logs from right after you got those messages?

relevent bit from seedvault-14-4.0-1718651594220.txt. ``` ruby 06-17 21:12:20.799 32718 337 E RestoreCoordinator: Error while getting restore set 1718570792674 06-17 21:12:20.799 32718 337 E RestoreCoordinator: java.io.IOException: java.io.IOException 06-17 21:12:20.799 32718 337...