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

Investigate why app preferences are stored in local storage by default instead of in the native app preferences #88

Open
shankari opened this issue Feb 22, 2016 · 0 comments

Comments

@shankari
Copy link
Contributor

While initializing the plugin, we planned to use shared preferences to check whether initialization was complete. The expectation was that the shared preferences would be set at the end of the onboarding process
https://github.com/e-mission/e-mission-phone/blob/master/www/js/intro.js#L108
and we could just use it.

This preference seems to be set correctly, because when we read it here:
https://github.com/e-mission/e-mission-phone/blob/master/www/js/controllers.js#L10
it is true after the first init, but while reading it from native code, it is false.

This is probably because the app preferences appear to use local storage by default. Need to file an issue and investigate in depth. For now, we simply set it from native code and move on.

But need to investigate further and determine whether we should use the app preferences plugin, or just go back to sqlite instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant