Delegate SecureVault KeyStore Events in All Scenarios #2827
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.
Task/Issue URL: https://app.asana.com/0/0/1207236816134198/f
Description:
Context
As part of ✓ macOS: Reduce Negative User Feedback Relating to Password Entry Prompts, we added Pixel event reporting for Keychain migrations. These events are reported via calls to SecureVaultReporter
Current Behavior
In some cases where an intermediate is used to communicate with SecureVaultReporter, we are not delegating SecureVault events
Expected Behavior
In all cases where an intermediate is used to communicate with SecureVaultReporter, we should delegate SecureVault events
Steps to test this PR:
Copy Testing:
’
rather than'
Orientation Testing:
Device Testing:
OS Testing:
Theme Testing:
Internal references:
Software Engineering Expectations
Technical Design Template