AndroidPreferences.flush() has no way to enforce synchronous saving about libgdx HOT 2 CLOSED

SharedPreferences handles android lifecycle phase changes automatically. The problem here is you're killing the process which ignores the Android lifecycle and can cause the kind of issues you describe.

You don't need to worry about Android component lifecycles and their interaction with apply() writing to disk. The framework makes sure in-flight disk writes from apply() complete before switching states.

Without knowing the details of your use case, generally speaking, restarting an Android app due to a settings change is not a good practice.

On the other hand SharedPreferences has some limitations that are overcome by some more modern alternatives such as Jetpack DataStore. I think it'd be a nice contribution to add a new alternative (and optional) Android Preferences DataStore based implementation.

from libgdx.

Thanks for the response. Well, I guess I have too much static state. At some point it makes sense to just restart the whole app instead of proper cleanup. Though I consider to do it it properly now.

from libgdx.