Commit Graph

10 Commits

Author SHA1 Message Date
Jordan Rose
1e7d61cf2d swift: Get our comments DocC-clean 2025-09-29 09:48:14 -07:00
Jordan Rose
9e2bcb2a74 SVRB: Distinguish "automatic retry" from "manual retry" errors
- Java: This distinction is already made, just reworded

- Node: We include "protocol errors" in IoError here, where retrying
  probably won't help, but it won't really be harmful either.

- Swift: Automatically retryable errors are now enumerated; other
  errors are still described as "manually retryable". (Also, fixed a
  redundant error message format call.)
2025-08-14 16:14:12 -07:00
Jordan Rose
dd5c2e2966 swift: Remove copy/pasted error descriptions for SvrB.store(...) 2025-08-13 16:02:58 -07:00
Jordan Rose
b4cd040474 Add SvrB.remove(), use it for app-level integration tests 2025-08-13 12:35:52 -07:00
Jordan Rose
fd8322b53e SVRB: Clarify what "chain" refers to in the doc comments 2025-08-07 17:28:02 -07:00
Jordan Rose
7cbdf26774 ffi: Align handling of svrb::Error::DecryptionError, document recovery
Java and Node treat DecryptionError like MetadataInvalid, since it's
more likely the metadata got corrupted than SVR did. Follow suit for
Swift, and then document the thrown errors like the other platforms.
2025-08-06 17:46:57 -07:00
Jordan Rose
be9e9a3ab6 Expose SvrB.createNewBackupChain(), make secret data non-optional 2025-07-31 12:37:02 -07:00
gram-signal
72935510d4 Immediately after a restore, use the same enc_salt/pw_salt for the next backup.
Co-authored-by: Jordan Rose <jrose@signal.org>
2025-07-30 20:14:26 -07:00
Alex Bakon
bb05cc016e Streamline bridging of SVR-B function arguments 2025-07-29 14:18:16 -04:00
Jordan Rose
7c9bc53358 Bridge SVR-B to Swift
Co-authored-by: Andrew <andrew@signal.org>
2025-07-28 13:21:18 -07:00