如何使用SharedPreferences？Android Studio布尔值数据丢失问题求解

Hey there! Let's tackle your questions about Android's SharedPreferences—super handy for storing small bits of data, right? Let's break it down step by step.

SharedPreferences is Android's built-in way to store key-value pairs for small, simple data (like booleans, strings, integers). Here's a straightforward workflow:

获取SharedPreferences实例 #

First, get an instance of SharedPreferences. You can use getSharedPreferences() with a custom name for app-wide access, or getPreferences() if you only need preferences for a single Activity:

// 全局共享的Preferences（所有组件都能访问，自定义名称）
SharedPreferences prefs = getSharedPreferences("MyAppPrefs", MODE_PRIVATE);
// 仅当前Activity使用的Preferences
SharedPreferences activityPrefs = getPreferences(MODE_PRIVATE);

Note: MODE_PRIVATE means only your app can access these preferences—this is the safest default for most cases.

写入/修改数据 #

To edit preferences, you need an Editor object. Make your changes, then save them with either apply() (async, recommended for non-critical saves) or commit() (sync, returns a boolean to confirm success):

SharedPreferences.Editor editor = prefs.edit();
editor.putString("username", "JohnDoe");
editor.putInt("userAge", 28);
editor.putBoolean("isDarkMode", true);

// 异步保存（不会阻塞主线程，优先推荐）
editor.apply();

// 或者同步保存（会阻塞主线程，但能直接知道是否保存成功）
boolean saveSuccess = editor.commit();

读取数据 #

To retrieve saved values, use the get[Type]() methods. Always provide a default value to fall back on if the key doesn't exist yet:

String username = prefs.getString("username", "Guest");
int userAge = prefs.getInt("userAge", 18);
boolean isDarkMode = prefs.getBoolean("isDarkMode", false);

保存布尔值 #

Saving a boolean follows the same pattern as other data types—here's a focused example:

// 初始化Preferences实例
SharedPreferences prefs = getSharedPreferences("MyPrefs", MODE_PRIVATE);
// 获取编辑器
SharedPreferences.Editor editor = prefs.edit();
// 写入布尔值
editor.putBoolean("hasLaunchedBefore", true);
// 保存修改
editor.apply();

为什么会出现"先false再true"的问题？ #

The issue you're seeing usually boils down to two common causes:

1. Default value fallback: On first launch, the key doesn't exist yet, so getBoolean() returns your specified default (false) before your code sets and saves the true value.
2. Async save timing: If you use apply() (which runs in the background) and immediately read the value right after, the save might not have finished—so you get the old/default value first.

解决方案 #

Let's fix both scenarios:

1. Check if the key exists before using the default value

Instead of relying on the default value, first verify if the key is already stored. This way, you only set the initial value once (on first launch):

SharedPreferences prefs = getSharedPreferences("MyPrefs", MODE_PRIVATE);
boolean hasLaunchedBefore;

if (prefs.contains("hasLaunchedBefore")) {
    // 键已存在，读取保存的值
    hasLaunchedBefore = prefs.getBoolean("hasLaunchedBefore", false);
} else {
    // 首次启动，设置为true并同步保存
    hasLaunchedBefore = true;
    SharedPreferences.Editor editor = prefs.edit();
    editor.putBoolean("hasLaunchedBefore", hasLaunchedBefore);
    editor.commit(); // 用commit()确保同步写入，避免后续读取拿不到最新值
}

// 现在hasLaunchedBefore会直接是true（首次启动）或保存的历史值（后续启动）

2. Use commit() for immediate sync (if you need to read right after saving)

If you need to access the updated boolean value immediately after saving, use commit() instead of apply(). commit() writes changes synchronously, so the next read will get the correct value:

SharedPreferences.Editor editor = prefs.edit();
editor.putBoolean("hasLaunchedBefore", true);
editor.commit(); // 同步保存，确保写入完成

// 马上读取就能拿到true
boolean value = prefs.getBoolean("hasLaunchedBefore", false);

3. Align read/write with Activity lifecycle

Make sure you're reading the value after you've saved it. For example, if you set the boolean in onCreate(), don't read it in a View's initializer that runs before the save completes. Instead, read it after the save operation, or in onStart()/onResume() where the app is fully initialized.

内容的提问来源于stack exchange，提问作者Gabriel