The following two chapters list all notable in-code changes of the XignSys SDK between version 5.0.0 and 5.0.1.
Fixed an issue where the XignSys SDK would discard the connection on some errors, although it is possible to recover from this state in the current step of the process. The affected error codes are:
XignSdkErrorCodes.alreadyInitializedXignSdkErrorCodes.identityManagerNotPersonalizedXignSdkErrorCodes.factorAlreadyPresentXignSdkErrorCodes.unsupportedFactorXignSdkErrorCodes.signingFailedXignSdkErrorCodes.missingSignedAuthenticatorXignSdkErrorCodes.connectionErrorXignSdkErrorCodes.unsupportedInputXignSdkErrorCodes.noRoleIsSelectedXignSdkErrorCodes.pinMissingXignSdkErrorCodes.deviceLockNotSetXignSdkErrorCodes.factorCreationFailedXignSdkErrorCodes.registrationCategoryMissingShared:
XignSdkErrorCodes.isRecoverable - Can be used to check whether it is possible to recover from
this error in the current step of the process.SDK:
DatabasePool to DatabaseQueue because it seems to produce QOS problems on iOS 16.0+.DEBUG builds, the XignSys SDK now accepts connections when the host is specified as IP address, even if the trust
anchor of the certificate is unknown to the system. This has been done to support self-signed certificates in
development environments. Note that the certificate must still be valid (correct format, not expired).