[v9.6.0] Update CHANGELOGs for macOS keychain fix #10181
Merged
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.
Context
Completely addressing #9392 required several PRs to eliminate the permission pop-ups on macOS:
The fix involved making the macOS keychain behave like the iOS-style keychain. The iOS-style keychain is sandboxed per application by default. This does not happen by default on macOS and requires using the
kSecUseDataProtectionKeychain
attribute when interacting with the Keychain. ThekSecUseDataProtectionKeychain
attribute tells macOS to treat a given keychain item like it is part of a keychain access group that the app knows and trusts. To synthesize and officiate this access group, it is required that macOS apps enable theKeychain Sharing
capability for targets that depend on Firebase.Fixes #9392