I am trying to diagnose an issue with my app in dealing with the key store. I will not go into the details because this is not the point of this Issues.
To understand what is happening I added console.log statements at critical steps, including when my module (the one, and only one importing react-native-keychain), is first loaded. That specific log is even before any import statement. To my surprise, the authentication prompt is given to the user even before my module is loaded. This raised a few questions
why is the authentication prompt is given even if nothing (on my part) is asking for access to the keystore
where is the prompt content coming from. The prompt is clearly from my code and not a system default
What if I really really really wanted my app to be fully initialized before any user interaction takes place?
In all likelihood, it the react-native-keychain Java binding that is doing some magic. Without trying to speculate if it is true, is it fair to say that such magic, if indeed it is true, should be documented? And, it should also be parametrize with at least an on/off flag.
I am trying to diagnose an issue with my app in dealing with the key store. I will not go into the details because this is not the point of this Issues.
To understand what is happening I added
console.logstatements at critical steps, including when my module (the one, and only one importing react-native-keychain), is first loaded. That specific log is even before any import statement. To my surprise, the authentication prompt is given to the user even before my module is loaded. This raised a few questionsIn all likelihood, it the react-native-keychain Java binding that is doing some magic. Without trying to speculate if it is true, is it fair to say that such magic, if indeed it is true, should be documented? And, it should also be parametrize with at least an on/off flag.
Or I have it all wrong......