fix(example): [SIW-1912] update native libraries fixing an issue related to integrity hardware key tag generation #177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…egrity hardware key generation
ale-mazz
changed the title
RiccardoMolinari95
approved these changes
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update native libraries fixing an issue related to integrity hardware key tag generation
List of Changes
@pagopa/io-react-native-integrityto 0.3.1io-react-native-secure-storagein favor of@pagopa/io-react-native-secure-storage0.2.0generateIntegrityHardwareKeyTagMotivation and Context
This has been done to align with IO App
How Has This Been Tested?
Tested on iPhone 13.
To test it, just try to create a WI and get the attestation.
Screenshots (if appropriate):
Checklist: