chore: [SIW-1632] Reuse the Wallet Instance Attestation in the example app #144
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.
List of Changes
This PR removes the need to get a new Wallet Instance Attestation every time there is a credential issuance.
Once the WIA is obtained, it is stored and persisted to the device via Secure Storage and then used for the credential issuance. The WIA is obtained again only when it expires.
This PR also introduces Secure Storage for WIA, PID and Credentials persistance.
Motivation and Context
Since new WIA requests on Android requires a Play Integrity API call, this change is required to reduce the Play Integrity API usage.
How Has This Been Tested?
Run the example app and check that the WIA is requested only once or when it is expired
Checklist: