ios: Keychain access denied when launched from notification about cordova-plugin-secure-storage HOT 7 CLOSED

Has the plugin been initialized? I am guessing not since you respond natively to the notification...

from cordova-plugin-secure-storage.

Does the plugin even need any initialization on ios? The constructor doesn't seem to do much other than setting the service. And yes, the success callback is executed before the get call is done.
I initialize the storage plugins on device ready and start the bootstrapping once this setup is done.

I've also tested using keychain mode "Always", which worked and also "AfterFirstUnlockThisDeviceOnly", which did not work.

from cordova-plugin-secure-storage.

All cordova plugins need initialization for the bridge to work.
But since you do things natively, you might have more luck with accessing the keychain natively as well. For iOS we barely use https://github.com/soffes/SSKeychain to do so.

from cordova-plugin-secure-storage.

@Alex-Sessler wrote that he initializes the plugin after the onDeviceReady event was fired, so Cordova did initialize the plugins. According to your securestorage.js code, there is not further initialization necessary after calling the SecureStorage constructor as you immediately call the success function:

var SecureStorageiOS = function (success, error, service) {
    this.service = service;
    setTimeout(success, 0);
    return this; 
};

We don't try to do anything natively. The Objective-C code above is just to show you how the app is launched when a user clicks the notification.
As stated by @Alex-Sessler the issue is that if there is a notification present and the cordova app is in a terminated state, the app will be launched by clicking on the notification (native code from 1st post) but in this state, we can't access the KeyChain in our cordova app.
Launching the app by clicking on the icon or selecting the notification when the app is paused or running does not have this issue. We are trying to figure out if this is an issue with the Plugin, Cordova or the method how the app is launched by the native code.

from cordova-plugin-secure-storage.

I see. It wasn't clear to me that the onDeviceReady was fired.
I am not sure why this would happen. In our own product Crypho we do the same thing and can access the keychain just fine.
Would it be possible to create a simple test-case with pinned versions and see if it is reproducable?

from cordova-plugin-secure-storage.

The latest changes (moving the work to threads) fixed this issue for me.

from cordova-plugin-secure-storage.

awesome :)

from cordova-plugin-secure-storage.