The following two chapters list all notable in-code changes of the XignSys SDK between version 5.1.0 and 5.2.0.
SDK:
XignSdkErrorCodes.biometricKeyWasPreviouslyRevoked - Which will be thrown the biometric key has
been previously revoked by the system or the app itself and BiometricCryptoManager.buildSignature.pushToken and wasRevoked to IdentityManagerEntity which can be used to gather more information about the
push token and biometric key status of the personalization/activation.BiometricCryptoManager.buildFactor can now throw XignSdkErrorCodes.identityManagerNotPersonalized and
XignSdkErrorCodes.biometricKeyWasPreviouslyRevoked errors.AuthenticationFactorState enum which is used as return parameter in getAuthenticationFactor().Personalizer.getAuthenticationFactorState() which can be used to receive the state of an authentication factor
of a given activation.sharedAsStateFlow to the companion object of the XignSdk which returns the current instance of
the XignSDK as read-only StateFlow.Authenticator.finishAuthentication/Synchronous. The functions raised
a XignSdkException with the error code XignSdkErrorCodes.MISSING_SIGNED_AUTHENTICATOR in case
an UserInformation objected has been passed which contains more signed authenticators than required. These
functions now accept UserInformation with more singed authenticators than required, like the XignSys iOS SDK
does.Parcel.readParcelable(loader:clazz:) did raise an exception when used to retrieve
a subclass of the ProcessInitializationData.Demo:
Revoke Biometrics to the identity managers option menu that can be used test the revocation
of a biometric factor manually.