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

Redesign AndroidPrefsAccessor to avoid deprecated preference sharing #24

Closed
udamken opened this Issue Aug 6, 2016 · 1 comment

Comments

1 participant
@udamken
Owner

udamken commented Aug 6, 2016

Context.MODE_MULTI_PROCESS is deprecated, a ContentProvider should be used. Also try to overcome always instantiating a new AndroidPrefsAccessor and AndroidContextAccessor.

@udamken udamken added this to the 3.0 milestone Sep 6, 2016

@udamken

This comment has been minimized.

Show comment
Hide comment
@udamken

udamken Sep 6, 2016

Owner

It turned out that Schedule and UpdateStatusNotification don't need to run in a different process by marking them with ":remote" in the AndroidManifest.xml. After changing that the SharedPreferences are no longer shared across different processes. So there's no need to redesign it more than this.

To be released with version 3.0.0.

Owner

udamken commented Sep 6, 2016

It turned out that Schedule and UpdateStatusNotification don't need to run in a different process by marking them with ":remote" in the AndroidManifest.xml. After changing that the SharedPreferences are no longer shared across different processes. So there's no need to redesign it more than this.

To be released with version 3.0.0.

@udamken udamken closed this Sep 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment