The error #711 indicates that SecItemAdd is being called when it should be SecItemUpdate in some users. This could be a case where (for some reason) errSecItemNotFound is returned from SecItemCopyMatching, but the value is actually saved.
Therefore, instead of SecItemCopyMatching, it has been modified to determine if the key is contains based on the value obtained by read.
This implementation is based on v9.0.0.
The error #711 indicates that
SecItemAdd
is being called when it should beSecItemUpdate
in some users. This could be a case where (for some reason)errSecItemNotFound
is returned fromSecItemCopyMatching
, but the value is actually saved.Therefore, instead of
SecItemCopyMatching
, it has been modified to determine if the key is contains based on the value obtained byread
. This implementation is based on v9.0.0.https://github.com/mogol/flutter_secure_storage/compare/v9.0.0...v9.1.0#diff-9ddc98846efcc4fe8d873eb548ed640010457abc988d46a2d2e2d421f8d29045L38
I would like to get your opinion on the modification.