"Could not decrypt data with alias: " #458

WilliamAlexander · 2021-05-03T19:40:28Z

Now and again I get the error:
"Could not decrypt data with alias: "

Happens when I call Keychain.getGenericPassword()
I don't use a service when calling Keychain.setGenericPassword (it uses the package name as default in Android).

Out of over 5k users, it happens for around 20 users (so far).
99% of the devices are Samsung.
Tried myself on a Samsung phone and I cannot recreate.

Not sure if related to the user:

resetting their keystore
running of space
I'm storing a json object (as string) and maybe some devices have a string len limit
other

I'll eventually update the react-native-keychain package but holding off as it might cause further issues in this field

"react-native": "0.64.0",
"react-native-keychain": "^6.2.0"

SudoPlz · 2022-01-03T16:25:46Z

Have you found any workarounds? i.e clear that alias entry from the keychain when that error occurs?

SudoPlz · 2022-01-03T18:02:26Z

Also have you noticed that it only happens on certain versions of react-native-keychain, but not on others?
cc @WilliamAlexander

WilliamAlexander · 2022-01-03T20:58:43Z

Also have you noticed that it only happens on certain versions of react-native-keychain, but not on others?
cc @WilliamAlexander

On "react-native-keychain": "^8.0.0", at the mo.
Happens now and again.
Thinking about moving to expo securestore at some point.
https://docs.expo.dev/versions/latest/sdk/securestore/

SudoPlz · 2022-01-03T21:43:07Z

Thanks for the answer @WilliamAlexander. We're investigating what it would take to move to securestore as well.

WilliamAlexander · 2022-01-03T23:53:59Z

Thanks for the answer @WilliamAlexander. We're thinking of moving to securestore as well.

That's interesting.
I was curious if any data I have in the keystores using this npm will be retrievable using the expo npm.
I'd be interested to know if you do decide to take this approach.

I like expo npm packages (not cli as it's too bulky) and they are well maintained

SudoPlz · 2022-01-20T14:45:12Z

@oblador hey Joel, I'm wondering if you're aware of the issue above, and if there are plans on fixing it.

lauriharpf · 2022-05-18T13:22:08Z

On "react-native-keychain": "^8.0.0", at the mo.

Also seeing the Could not decrypt data with alias: error on 8.0.0. This issue and #430 might be related, #430 mentions Could not encrypt data with alias.

Considering patching react-native-keychain with https://www.npmjs.com/package/patch-package in our project by applying https://github.com/mattermost/mattermost-mobile/blob/master/patches/react-native-keychain%2B8.0.0.patch , which introduces a cache for the keychain.

lauriharpf · 2022-06-01T11:51:27Z

Considering patching react-native-keychain with https://www.npmjs.com/package/patch-package in our project by applying https://github.com/mattermost/mattermost-mobile/blob/master/patches/react-native-keychain%2B8.0.0.patch , which introduces a cache for the keychain.

Patched. The Could not decrypt data with alias errors still appear even with the patch. I don't currently have enough data to say if the patch affects the frequency of the errors, but at least it doesn't completely eliminate the error.

savv · 2022-08-08T07:59:05Z

Just FYI - we saw this error on a Google Pixel 4a running Android 12.

Versions:

    "react-native": "0.68.2",
    "react-native-keychain": "8.1.1",

kreonjr · 2022-08-22T02:22:27Z

We have had had multiple users report this happening pretty often on Android. The ones that also reported device and api were:

Google Pixel 3 API 28
Motorola G Power, android ver. 11

"react-native": "0.66.1",
"react-native-keychain": "8.1.1"

Patch suggestion attempted but didn't work on our Google Pixel 2 API 30 test device.

ilyagru · 2022-08-26T14:16:02Z

Having the exact same issue! Is there a workaround?

Only Android and mostly Samsung devices.

"react-native": "0.69.2",
"react-native-keychain": "^8.1.1",

nicwise · 2022-09-15T21:43:49Z

related to #567 I think :(

viLeeKorn · 2022-11-24T15:33:20Z

faced the same issue on S22, Pixel 7, Xiaomi Redmi Note 9 Pro

"react-native": "0.68.2",
"react-native-keychain": "^8.0.0",

aliza-khu · 2023-09-18T06:57:03Z

Is there any workaround for this? Then please share.

davidecarpini · 2023-10-10T07:26:40Z

any updates on this?

c-goettert · 2023-10-17T14:51:06Z

We are now seeing this more often as well, one of our users stated it happened after upgrading his Samsung (S21+) to the latest android version.

lucasftcruz · 2023-10-18T14:58:18Z

The same issue here, Could not decrypt data with alias: for the devices below all running Android 13:

SM-G990E
SM-G998B
SM-G991U
SM-G996B
SM-G991B
Pixel 4a

Ernst2106 · 2023-10-18T19:13:27Z

I have the same issue with XUMM
My device: SM-G991B/DS
Last update: today (18 October)

Error message: "Could not decrypt data with alias: xumm-realm-key: java.security. InvalidKeyException: Keystore operation failed".

Is there a fix for this issue?

seanquinn · 2023-10-19T08:32:40Z

Also getting reports from users of this error in the last week 👍

Frans-L · 2023-10-19T13:49:25Z

We have also started to see crash reports from our customers with the Samsung SM-G991B.

Does anyone know any workaround?

TwistedMinda · 2023-10-19T17:18:28Z

Same here, Samsung SM-G991B is the problem.
Using latest version : react-native-keychain 8.1.2

Seems to appear more frequently than before without any specific change from our side

yberstad · 2023-10-19T21:58:05Z

@TwistedMinda, we have seen a sudden increase of this error the last few days, starting to pick up on the 11th of October. Could it be that Samsung is rolling out a security fix that makes this issue worse?
@TwistedMinda, are you able to reproduce it?

These are the devices we are experience this on:

TwistedMinda · 2023-10-19T22:30:13Z

@yberstad No we don't have access to the specific device to reproduce.
Can't confirm 11th either, we're seeing an urge from 19th, but we don't have many users with the problem.
I don't think I can help more as we really don't have a lot of occurences.
I can only confirm that it is becoming more frequent, with no apparent change coming from us!

I think a Samsung update is the most straightfoward reason, what else could have changed?

No user complained either. We'll keep an eye on it 👀

yberstad · 2023-10-19T22:36:32Z

@TwistedMinda, thanks for your quick response.

We are starting to get customer complaints regarding this, so we'll try to investigate further.

If we find workaround I'll let you know.

Ernst2106 · 2023-10-20T10:06:56Z

I can confirm that it happened straight after installing Samsung's latest update (including security patch 1 October 2023) on my Galaxy S21 5G.
I have preliminary 'solved' the issue by resetting Xumm's app data and re-importing my wallets.
Xumm now functions normally. This solution would appear suboptimal to me, however.

TwistedMinda · 2023-10-20T22:52:02Z

Good to know, thanks for reporting! So that's a good news, it means the bug only happens once, when the data are already on the device, and further resetting the values don't cause problems. So supposedly the update messed up a specific space in memory, but only at installation time... Right?

Of course the need to reset app data depends on the implementation of catching the underyling error.
We have a fallback in case of this error that doesn't block the user, so they don't need to reset app data.

alexandrius · 2023-10-25T22:02:22Z

For anyone who wants to reproduce. You gotta have affected device. I have Galaxy S21 FE - which is also affected.

Go to https://samfw.com/imei to find your device region
Then search for the device (Make sure the device model is correct)
Choose your region - mine was UAE
Download a firmware one version older than the latest. For me it was G990EXXS7EWH5.
Now you either need to find a Windows computer or try Heimdall - whatever it is I haven't tried
Follow these instructions for Windows: https://www.youtube.com/watch?v=4SjiCbDRmU4
Wait for reboot, setup etc
Now install the affected app (I only tested self-signed prod version, I can read the logs. Didn't risk debug).
Launch the app and make sure the Keys are generated.
Now go to System settings and start downloading latest firmware
After it's installed the keys will be broken.

What I found so far. KeyMaster seems to be updated to V4. KeyMaster considers the key need to be updated - whatever it means. The update fails for no understandable (at least to me) reason. The error originates here.

Logcat output

10-25 22:46:16.458  7851  7913 D RNKeyChain: com.oblador.keychain.exceptions.CryptoFailedException: Could not decrypt bytes: Keystore operation failed
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decryptBytes(CipherStorageKeystoreAESCBC.java:248)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decrypt(CipherStorageKeystoreAESCBC.java:188)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.KeychainModule.decryptCredentials(KeychainModule.java:139)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.KeychainModule.getGenericPasswordForOptions(KeychainModule.java:118)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.KeychainModule.getInternetCredentialsForServer(KeychainModule.java:211)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at java.lang.reflect.Method.invoke(Native Method)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:151)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.os.Handler.handleCallback(Handler.java:942)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.os.Handler.dispatchMessage(Handler.java:99)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.os.Looper.loopOnce(Looper.java:226)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.os.Looper.loop(Looper.java:313)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at java.lang.Thread.run(Thread.java:1012)
10-25 22:46:16.458  7851  7913 D RNKeyChain: Caused by: java.security.InvalidKeyException: Keystore operation failed
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.keystore2.KeyStoreCryptoOperationUtils.getInvalidKeyException(KeyStoreCryptoOperationUtils.java:130)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.keystore2.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:154)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:345)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:240)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2981)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher.tryCombinations(Cipher.java:2892)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2797)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher.chooseProvider(Cipher.java:774)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher.init(Cipher.java:1289)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at javax.crypto.Cipher.init(Cipher.java:1224)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decryptBytes(CipherStorageKeystoreAESCBC.java:244)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	... 15 more
10-25 22:46:16.458  7851  7913 D RNKeyChain: Caused by: android.security.KeyStoreException: Invalid key blob (internal Keystore code: -33 message: In create_operation: Failed to begin operation. 10328
10-25 22:46:16.458  7851  7913 D RNKeyChain: 
10-25 22:46:16.458  7851  7913 D RNKeyChain: Caused by:
10-25 22:46:16.458  7851  7913 D RNKeyChain:     0: In KeystoreSecurityLevel::upgrade_keyblob_if_required_with.
10-25 22:46:16.458  7851  7913 D RNKeyChain:     1: In utils::upgrade_keyblob_if_required_with: Calling km_op.
10-25 22:46:16.458  7851  7913 D RNKeyChain:     2: Error::Km(ErrorCode(-33))) (public error code: 10 internal Keystore code: -33)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:418)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.KeyStoreSecurityLevel.createOperation(KeyStoreSecurityLevel.java:123)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:340)
10-25 22:46:16.458  7851  7913 D RNKeyChain: 	... 23 more
10-25 22:46:16.458  7851  7913 W System.err: com.oblador.keychain.exceptions.CryptoFailedException: Could not decrypt bytes: Keystore operation failed
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decryptBytes(CipherStorageKeystoreAESCBC.java:248)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decrypt(CipherStorageKeystoreAESCBC.java:188)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.KeychainModule.decryptCredentials(KeychainModule.java:139)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.KeychainModule.getGenericPasswordForOptions(KeychainModule.java:118)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.KeychainModule.getInternetCredentialsForServer(KeychainModule.java:211)
10-25 22:46:16.458  7851  7913 W System.err: 	at java.lang.reflect.Method.invoke(Native Method)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:151)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.os.Handler.handleCallback(Handler.java:942)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.os.Handler.dispatchMessage(Handler.java:99)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.os.Looper.loopOnce(Looper.java:226)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.os.Looper.loop(Looper.java:313)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
10-25 22:46:16.458  7851  7913 W System.err: 	at java.lang.Thread.run(Thread.java:1012)
10-25 22:46:16.458  7851  7913 W System.err: Caused by: java.security.InvalidKeyException: Keystore operation failed
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.keystore2.KeyStoreCryptoOperationUtils.getInvalidKeyException(KeyStoreCryptoOperationUtils.java:130)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.keystore2.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:154)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:345)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:240)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2981)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher.tryCombinations(Cipher.java:2892)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2797)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher.chooseProvider(Cipher.java:774)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher.init(Cipher.java:1289)
10-25 22:46:16.458  7851  7913 W System.err: 	at javax.crypto.Cipher.init(Cipher.java:1224)
10-25 22:46:16.458  7851  7913 W System.err: 	at com.oblador.keychain.cipherStorage.CipherStorageKeystoreAESCBC.decryptBytes(CipherStorageKeystoreAESCBC.java:244)
10-25 22:46:16.458  7851  7913 W System.err: 	... 15 more
10-25 22:46:16.458  7851  7913 W System.err: Caused by: android.security.KeyStoreException: Invalid key blob (internal Keystore code: -33 message: In create_operation: Failed to begin operation. 10328
10-25 22:46:16.458  7851  7913 W System.err: 
10-25 22:46:16.458  7851  7913 W System.err: Caused by:
10-25 22:46:16.458  7851  7913 W System.err:     0: In KeystoreSecurityLevel::upgrade_keyblob_if_required_with.
10-25 22:46:16.458  7851  7913 W System.err:     1: In utils::upgrade_keyblob_if_required_with: Calling km_op.
10-25 22:46:16.458  7851  7913 W System.err:     2: Error::Km(ErrorCode(-33))) (public error code: 10 internal Keystore code: -33)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:418)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.KeyStoreSecurityLevel.createOperation(KeyStoreSecurityLevel.java:123)
10-25 22:46:16.458  7851  7913 W System.err: 	at android.security.keystore2.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:340)
10-25 22:46:16.458  7851  7913 W System.err: 	... 23 more
10-25 22:46:16.458  7851  7913 E RNKeychainManager: Unknown error: Could not decrypt bytes: Keystore operation failed

Any input is highly appreciated

androideveloper · 2023-10-26T07:01:07Z

Hi @alexandrius ! Thanks for sharing this! Have you tried the encrypt operation?

alexandrius · 2023-10-26T07:03:04Z

@androideveloper Can you please clarify what do you mean?
Are you asking if encrypt still works?

androideveloper · 2023-10-26T07:04:51Z

Yes! I guess it fails as well

alexandrius · 2023-10-26T07:07:02Z

@androideveloper I haven't tried but I think it will go through since it deletes previous master key. Seems like the Keys can be damaged and it's somehow related to hardware Exynos 2100 in my case

N3TC4T · 2023-10-26T09:12:33Z

@TwistedMinda @Ernst2106 @yberstad @lucasftcruz @c-goettert

Samsung just released another update yesterday and I can confirm it fixes the issue.

androideveloper · 2023-10-26T10:48:51Z

@N3TC4T the security patch level in the picture is still Oct 1 though 🤔 did they release multiple patches for October?

matt-alice · 2023-10-26T11:03:35Z

Same concern - I only downloaded the latest security update 2 days ago while trying to reproduce the issue (Galaxy A32 5G). My security update is dated October 24th, but I think it means "downloaded October 24th". The patch itself was from August 2023.

Are there other patches for October?

alexandrius · 2023-10-26T11:08:55Z

@matt-alice there are patches from october, however I don't think the patch was faulty but rather crappy Samsung code on top of it

N3TC4T · 2023-10-26T11:24:50Z

the security patch level in the picture is still Oct 1 though 🤔 did they release multiple patches for October?

@androideveloper it's another update, which has been released yesterday.

mhv1 · 2023-10-26T11:29:31Z

Seems to be that updates are rolled out at different times depending on the region and under these really confusing version numbers.

I did find a page were you can see the list of releases currently available for a specific model in a specific region. For example, my affected device model number is: Galaxy S21 FE 5G (SM-G990B2), Googling that + "updates", I get the following site in the results:

https://doc.samsungmobile.com/SM-G990B2/EUX/doc.html

The "EUX" part in the URL denotes the region. Looking at the release date (and not at "Security patch level") looks like the latest patch that fixes the issue (i.e., something released yesterday) is not yet available in Europe.

hugoalvares · 2023-10-27T17:38:40Z

We're getting a JSON parse error when parsing a stored JSON string from Keychain.
It seems that the cause is that there are invalid characters being added to the JSON string (not sure if at the start or end).
Here's a workaround that we're using for now:
JSON.parse(tokens.substring(tokens.indexOf('{'), tokens.lastIndexOf('}') + 1))

bpeltonc · 2023-10-27T17:41:02Z

I will add this isn't happening only on Samsung devices. I have tons of Sentry reports of this error with Pixel devices. I wonder if anybody can confirm this same error doesn't occur with the Expo Secure Store library? I'm considering using that instead as well, but I don't know it's just this library.

In case anybody is curious, I'm no longer having any trouble with this, or any error at all, after migrating to Expo Secure Store. It does appear to be related to the way this library interacts with the native APIs and not the native APIs themselves.

alexandrius · 2023-10-27T17:43:36Z

@bpeltonc this library is fine. By moving to expo-secure-store you just recreated all the keys. Recreating keys is what "fixed" the problem.

Tejesh-Duvvuru · 2023-11-01T12:28:24Z

Hi, do we have any solution to resolve this error.

Ernst2106 · 2023-11-01T17:17:16Z

Samsung released a new update, which fixes this issue

Tejesh-Duvvuru · 2023-11-02T06:10:44Z

Hi, @Ernst2106, we are using an open-source version of Android 10 and Android 6. We are encountering this error.

filipef101 · 2023-11-02T11:37:02Z

Hi, @Ernst2106, we are using an open-source version of Android 10 and Android 6. We are encountering this error.

Maybe needs an update?

argenkiwi · 2023-11-05T20:09:31Z

There is a known and outstanding issue and the suggested workaround is to recreate the keys as @alexandrius suggested.

danibonilha · 2023-12-12T16:43:34Z

Also having users experiencing this issue on Pixel 5 - Android 14, but not all of them.
Was anyone able to reproduce this issue on an emulator ? Or found any other workaround to decrypt the data and migrate it without losing it ?

liufengwei · 2024-01-05T03:55:36Z

arlovip · 2024-01-18T12:16:16Z

The same issue happens on XiaoMi 12 Pro device(Android 13). This happens when the faceId is turned on while the fingerprint is turned off.

tomerh2001 · 2024-02-25T09:24:25Z

Also experiencing this, any workarounds?

fkranenburg · 2024-02-26T15:00:24Z

We have the same issue. We found out, when switching phones Android 'restores' your apps. Some apps also restore their internal caches, probably coming from the google cloud. And after this restore it gets corrupted... Probably the same after some phone updates as well.

c-goettert · 2024-06-20T08:10:37Z

We are starting to see a sudden increase of this error again in one of our apps, on all kinds of android devices (mostly android 14)..

mwmcode · 2024-06-20T08:13:38Z

if it's the same as expo's secure-storage issue, then maybe this can help?

expo/expo#23426 (comment)

We found an issue related to SharedPreferences being backed up by automatic backup and being restored when re-installing the app, which would cause decryption errors as after uninstalling the app the KeyStore is cleared, which makes them impossible to decrypt.

tomDubrovsky · 2024-08-25T12:45:20Z

HERE IS A SOLUTION
u can simulate this issue on android studio simulator,
first u have to root it (https://medium.com/@lightbulbr/how-to-root-an-android-emulator-with-tiramisu-android-13-f070a756c499)
then after u loged in do
adb shell
su
cd /data/misc/keystore/user_0 and delete ..._USRPKEY_ACCESS_TOKEN
tahts how u can see it and u can handle it in the code like this

`import { SecureStorage } from "./secureStorage";

export async function getAccessToken() {
    try {
        const key = SecureStorage.keys.ACCESS_TOKEN;
        const token = await SecureStorage.getSecureValue(key);
        return token;
    } catch (e) {

        if (e.message == 'Could not decrypt data with alias: ACCESS_TOKEN') {
            const key = SecureStorage.keys.ACCESS_TOKEN;
            await SecureStorage.removeSecureValue(key);
            return null;
        } else {
            throw e;
        }
    }
}`

developius mentioned this issue Jul 8, 2021

Android: init keyStore error consistently, sometimes fail, and then success again #436

Open

kreonjr mentioned this issue Aug 23, 2022

Added an alert that will suggest to the user to reset their app data podverse/podverse-rn#1178

Merged

stetbern mentioned this issue Aug 25, 2022

"Could not decrypt data with alias: #ServiceName" after Android 13 update #565

Closed

lucasftcruz mentioned this issue Oct 23, 2023

Encrypt and decrypt failing on latest Samsung OS #617

Closed

alexandrius mentioned this issue Oct 25, 2023

E_CRYPTO_FAILED on Android 13 and Pixel phones. AES crashing out while decrypting. #567

Open

DorianMazur self-assigned this Oct 24, 2024

yberstad mentioned this issue Nov 5, 2024

Cold start on android took 5-10 seconds longer than before the library update #630

Closed

"Could not decrypt data with alias: " #458

"Could not decrypt data with alias: " #458

Comments

WilliamAlexander commented May 3, 2021

SudoPlz commented Jan 3, 2022 • edited Loading

SudoPlz commented Jan 3, 2022

WilliamAlexander commented Jan 3, 2022

SudoPlz commented Jan 3, 2022 • edited Loading

WilliamAlexander commented Jan 3, 2022

SudoPlz commented Jan 20, 2022

lauriharpf commented May 18, 2022

lauriharpf commented Jun 1, 2022

savv commented Aug 8, 2022

kreonjr commented Aug 22, 2022

ilyagru commented Aug 26, 2022

nicwise commented Sep 15, 2022

viLeeKorn commented Nov 24, 2022

aliza-khu commented Sep 18, 2023

davidecarpini commented Oct 10, 2023

c-goettert commented Oct 17, 2023

lucasftcruz commented Oct 18, 2023 • edited Loading

Ernst2106 commented Oct 18, 2023 • edited Loading

seanquinn commented Oct 19, 2023

Frans-L commented Oct 19, 2023

TwistedMinda commented Oct 19, 2023

yberstad commented Oct 19, 2023 • edited Loading

TwistedMinda commented Oct 19, 2023 • edited Loading

yberstad commented Oct 19, 2023

Ernst2106 commented Oct 20, 2023

TwistedMinda commented Oct 20, 2023 • edited Loading

alexandrius commented Oct 25, 2023 • edited Loading

androideveloper commented Oct 26, 2023

alexandrius commented Oct 26, 2023

androideveloper commented Oct 26, 2023

alexandrius commented Oct 26, 2023

N3TC4T commented Oct 26, 2023

androideveloper commented Oct 26, 2023

matt-alice commented Oct 26, 2023

alexandrius commented Oct 26, 2023

N3TC4T commented Oct 26, 2023

mhv1 commented Oct 26, 2023 • edited Loading

hugoalvares commented Oct 27, 2023

bpeltonc commented Oct 27, 2023

alexandrius commented Oct 27, 2023

Tejesh-Duvvuru commented Nov 1, 2023 • edited Loading

Ernst2106 commented Nov 1, 2023

Tejesh-Duvvuru commented Nov 2, 2023

filipef101 commented Nov 2, 2023

argenkiwi commented Nov 5, 2023

danibonilha commented Dec 12, 2023

liufengwei commented Jan 5, 2024

arlovip commented Jan 18, 2024 • edited Loading

tomerh2001 commented Feb 25, 2024

fkranenburg commented Feb 26, 2024

c-goettert commented Jun 20, 2024

mwmcode commented Jun 20, 2024

tomDubrovsky commented Aug 25, 2024 • edited Loading

SudoPlz commented Jan 3, 2022 •

edited

Loading

SudoPlz commented Jan 3, 2022 •

edited

Loading

lucasftcruz commented Oct 18, 2023 •

edited

Loading

Ernst2106 commented Oct 18, 2023 •

edited

Loading

yberstad commented Oct 19, 2023 •

edited

Loading

TwistedMinda commented Oct 19, 2023 •

edited

Loading

TwistedMinda commented Oct 20, 2023 •

edited

Loading

alexandrius commented Oct 25, 2023 •

edited

Loading

mhv1 commented Oct 26, 2023 •

edited

Loading

Tejesh-Duvvuru commented Nov 1, 2023 •

edited

Loading

arlovip commented Jan 18, 2024 •

edited

Loading

tomDubrovsky commented Aug 25, 2024 •

edited

Loading