Unlike commit(), which writes its preferences out to persistent storage synchronously, apply() commits its changes to the in-memory SharedPreferencesimmediately but starts an asynchronous commit to disk and you won't be notified of any failures. If another editor on this SharedPreferences does a regularcommit() while a apply() is still outstanding, the commit() will block until all async commits are completed as well as the commit itself.


Unlike commit(), which writes its preferences out to persistent storage synchronously, apply() commits its changes to the in-memory SharedPreferencesimmediately but starts an asynchronous commit to disk and you won't be notified of any failures. If another editor on this SharedPreferences does a regularcommit() while a apply() is still outstanding, the commit() will block until all async commits are completed as well as the commit itself.