Details:
- Version of Mobile SDK Used: 9.1.0
- Issue found in Native App or Hybrid App: Native
- OS Version: 14,15
- Device: all
- Steps to reproduce: random
- Actual behaviour: SFSDKCryptoUtils randomly throws error.
- Expected Behavior: No errors should be thrown.
- Error Log: See below
From time to time we had sporadic error that threw from the SFSDK:
SFSDKCryptoUtils Error decrypting data with EC key. Error code: The operation could not be completed. (CryptoTokenKit error -2.)
or
SFSDKCryptoUtils Error decrypting data with EC key. Error code: The operation could not be completed. (CryptoTokenKit error -7.)
Which eventually would fail all SF Api requests with "INVALID_AUTH_HEADER" error while keeping user logged in.
This could happen during usage of the App, and we could not see particular patterns which precedes the error. Restarting the App won't help.
Also, we already have set KeychainHelper.setAccessibleAttribute(.afterFirstUnlock) in the app delegate during app startup.
Details:
From time to time we had sporadic error that threw from the SFSDK:
SFSDKCryptoUtils Error decrypting data with EC key. Error code: The operation could not be completed. (CryptoTokenKit error -2.)or
SFSDKCryptoUtils Error decrypting data with EC key. Error code: The operation could not be completed. (CryptoTokenKit error -7.)Which eventually would fail all SF Api requests with "INVALID_AUTH_HEADER" error while keeping user logged in.
This could happen during usage of the App, and we could not see particular patterns which precedes the error. Restarting the App won't help.
Also, we already have set KeychainHelper.setAccessibleAttribute(.afterFirstUnlock) in the app delegate during app startup.