Feat: Add keychainAccessGroup
configuration option
#36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an optional configuration option
keychainAccessGroup
which sets thekeychain-access-groups
entitlement on both the main app and the widget during prebuild.This entitlement is similar to #7 in both purpose and implementation, but while App Groups are typically used to insecurely share key/value pairs between an app and a widget,
keychain-access-groups
allow you to use packages likeexpo-secure-store
to securely share values via the iOS Keychain.Here's an example of implementing this in Swift:
And implementing writing the item to the keychain in React Native: