Question 1

How to securely store a password using SecurePropertyStorage?

Accepted Answer

Use the @Keychain wrapper with a store key, e.g., @Keychain("password") var password: String?. This automatically encrypts the value with AES-GCM and stores it in the Keychain, leveraging Apple's secure storage. For non-optional values, use @UnwrappedKeychain with a default value.

Question 2

SecurePropertyStorage vs SwiftKeychainWrapper: which is better?

Accepted Answer

SecurePropertyStorage offers automatic encryption and hashing out-of-the-box, plus property wrapper convenience and DI features, making it more comprehensive for secure storage. SwiftKeychainWrapper is simpler and more lightweight if you only need basic Keychain access without encryption or additional abstractions. Choose based on whether you need built-in security automation or minimal dependencies.

Question 3

How to make a custom type Sendable for use with SecurePropertyStorage?

Accepted Answer

Ensure your type conforms to the Sendable protocol by making it a value type (struct) or a class with immutable properties and @unchecked Sendable if needed. For Codable types, add Sendable conformance explicitly, and check Swift's concurrency guidelines to avoid data races when storing instances.

Question 4

Can I disable encryption for certain properties in SecurePropertyStorage?

Accepted Answer

No, encryption is automatic and mandatory for all values stored using the library's wrappers, as stated in the README. If you need non-encrypted storage, you might have to use raw UserDefaults or Keychain APIs separately, which defeats the purpose of this library's security-first approach.

Question 5

How to use dependency injection with SecurePropertyStorage in a SwiftUI app?

Accepted Answer

Register dependencies with @Register in an app initializer or Injector class, then inject them with @Inject in SwiftUI views or view models. Use qualifiers for multiple implementations, and ensure concurrency safety by making dependencies Sendable. The README provides examples with qualifiers and scopes for flexible DI.

Question 6

What are the performance implications of using SecurePropertyStorage?

Accepted Answer

Performance can be impacted due to automatic AES-GCM encryption and SHA512 key hashing on every read/write, which adds overhead compared to plain storage. For high-frequency data access or large datasets, this might slow down operations, so benchmark for your use case and consider if the security trade-off is necessary.

SecurePropertyStorage

What is SecurePropertyStorage?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions