Actually, the save preferences code was factored into its own method
and there was a commit. The two lifecycle methods were simply calling
it. This is why it appeared to me to be a threading issue in the
lifecycle callbacks
On Dec 19, 6:05 pm, Mark Murphy wrote:
> stanlick wrote:
> > SharedPref
stanlick wrote:
> SharedPreferences.Editor editor = settings.edit(); returns
> android.app.ApplicationContext$SharedPreferencesImpl
> $editori...@447d10e8 which resolves to a backing HashMap. When I was
> saving preferences from both lifecycle methods, it was missing the
> last "key" that was "put
SharedPreferences.Editor editor = settings.edit(); returns
android.app.ApplicationContext$SharedPreferencesImpl
$editori...@447d10e8 which resolves to a backing HashMap. When I was
saving preferences from both lifecycle methods, it was missing the
last "key" that was "put."
On Dec 19, 1:05 pm, Ma
3 matches
Mail list logo