Open danielgek opened 7 years ago
Hi @danielgek I just ran into the same issue. Did you figure it out? I'll take a look as well..
Ah, I think the rootcause is this line.
@EddyVerbruggen i haven't touched on this in a while(working on big rewrite), and yes, that line seams to be the root cause
do you have any idea how to fix it ?
Working on it.. that line was from the plugin seed I used. Changing it to .android instead gets the job done, but looking for the best approach.
Status update: I really hate webpack right now.
Status update: I've tried different things but didn't find a good alternative.
For the momentI'm just changing .ios
to .android
in index.d.ts
in node_modules/nativescript-secure-storage
. Yes that sucks, but I think it's a temporary glitch in the webpack bundler logic.
I noticed that when I injected the plugin class in a @Component
constructor
I would run into problems, but when you simply do new SecureStorage
there is no problem.
So i was in the process of getting webpack/aot working in an application, and something weird happened: when i try to use the securestorage i got the following error:
after investigating the bundle.js i saw that it contains the two implementations and on android it uses the ios one:
@EddyVerbruggen do you have any idea of what could it be ?