Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keychain entry not found #46

Closed
vaibhawc opened this issue Dec 10, 2016 · 7 comments
Closed

Keychain entry not found #46

vaibhawc opened this issue Dec 10, 2016 · 7 comments

Comments

@vaibhawc
Copy link

Hi,
I get this error sometimes while getting generic password : "Keychain entry not found"
I am unable to reproduce it. Do you have an idea what could be causing it.
It only occurs sometimes and I cannot reproduce it. Could it because of that keychain sharing problem?
Please help asap, as this is occurring in production app being used by eminent doctors.

@siwonia
Copy link

siwonia commented Feb 3, 2017

Hi @vaibhawc, could you solve the problem? We are fighting with the same issue.

@parronGroupnote
Copy link

same issue

@parronGroupnote
Copy link

@vaibhawc @schultka I was getting this error on Android only. I managed empty credentials inside the promise resolving with an if "if(credentials){}else{}". The solution was to use the "catch" for the promise rejection when no credentials where found and it worked

@siwonia
Copy link

siwonia commented Feb 13, 2017

@parronator yep, I'm also catching, if there are no credentials, but this is not the error. From time to time there are no credentials, even though the Keychain.setGenericPassword resolved a success. I implemented an ugly workaround, that also saves the data in Reacts AsyncStorage. If Keychain.getGenericPassword fails, my services tries to get the data from AsyncStorage and saves the data in Keychain again. Well, that's really dirty but it works. Strange bug.

@vonovak
Copy link
Collaborator

vonovak commented Mar 5, 2017

related: #57

@oblador
Copy link
Owner

oblador commented Apr 4, 2017

The android inconsistency/bug should be fixed in 1.2.0. Can anyone confirm that this issue is fixed?

@vonovak
Copy link
Collaborator

vonovak commented Aug 30, 2018

closing for inactivity, please open a new issue in case you meet this

@vonovak vonovak closed this as completed Aug 30, 2018
Repository owner locked as resolved and limited conversation to collaborators Aug 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants