React-native-keychain: Error: Could not encrypt data for service RN_KEYCHAIN_DEFAULT_ALIAS

Created on 28 Oct 2018 · 11Comments · Source: oblador/react-native-keychain

Keychain is working perfectly fine in iOS, but no luck in Android. I am totally blocked by this. What seems the problem with my code? Can you help me guys?

Error: Could not encrypt data for service RN_KEYCHAIN_DEFAULT_ALIAS

```
const allValues = await readKeychain();
try{
await Keychain.setGenericPassword('mykey','value', {
accessible: Keychain.ACCESSIBLE.WHEN_UNLOCKED_THIS_DEVICE_ONLY,
});
}catch(e){
// I logged it here
}

Source

dnt-andinieves

👍1

Most helpful comment

👍 bump!

chaudhryjunaid on 7 Feb 2019

👍7 😄1

All 11 comments

We've seen this issue on a Sony Xperia, Running Android 8.0.0. It appears device specific at this stage. Other Android users with a range of devices are fine.

Issue appears to be here.

Unfortunately, our error tracking isn't passing the actual error which is thrown, just the CryptoFailedException with a generic description.

pscarey on 29 Oct 2018

👍1

Can anything be done for this? It's happening on Nexus 5X - 8.1.0 emulator as well.

jinshin1013 on 9 Nov 2018

👍1

I just started to have this problem. I was running 8.1.0 on a Nexus 5X on the emulator and out of nowhere this error popped up. It would be nice to have an update on this error...

tomasmedina on 27 Nov 2018

👍2

I am having this same issue on Nexus 5X emulator 8.1.0.

zigzactly on 3 Dec 2018

👍1

Same issue on Nexus 5X emulator (Android 8.1.0), running react-native 0.57.8 with react-native-keychain 3.0.0. Any fixes for this yet?

jamesmcn1 on 31 Jan 2019

There are now 6 people having this issue. If you can reproduce the issue, you can also fix it :) It would be great if someone could step up, fix it and submit a PR. Thanks.

vonovak on 31 Jan 2019

So, i don't know if it is exactly related since my code differs from the snippet @dnt-andinieves posted but i was getting this when password/value content got bigger, i can't say exactly at which point, but a content shortening/downsizing made the error "disappear".