Firebase CurrentUser为Null，如何在所有页面保持用户登录状态？

Great question! Let's break this down step by step to get your blog app's user session working reliably.

Is finish() on the Registration Page the Issue? #

Short answer: No. Calling finish() just destroys the registration activity instance—it doesn't directly cause CurrentUser to be null in other activities. The real problem is that you're not persisting the user's session data across app components. In-memory variables like CurrentUser don't survive activity transitions or app restarts unless you explicitly save and retrieve them.

How to Maintain Login State Across All Pages #

Here are the most practical, reliable methods to keep CurrentUser accessible everywhere in your app:

1. Use SharedPreferences for Basic Session Data #

SharedPreferences is perfect for storing simple user details (like ID, email, or an auth token) that you need to quickly retrieve across activities.

Save User Data After Registration:

// In your registration activity, right after successful sign-up
val sharedPref = getSharedPreferences("BlogAppSession", Context.MODE_PRIVATE)
with(sharedPref.edit()) {
    putString("user_id", currentUser.id)
    putString("user_email", currentUser.email)
    putString("user_username", currentUser.username)
    apply() // Use apply() for async save, commit() for sync operations
}

Load User Data in Other Activities:

Add this code to the onCreate() method of every activity that needs CurrentUser:

val sharedPref = getSharedPreferences("BlogAppSession", Context.MODE_PRIVATE)
val userId = sharedPref.getString("user_id", null)

if (userId != null) {
    // Recreate your CurrentUser object from stored data
    currentUser = User(
        id = userId,
        email = sharedPref.getString("user_email", "")!!,
        username = sharedPref.getString("user_username", "")!!
    )
} else {
    // No session exists—redirect to registration/login
    startActivity(Intent(this, RegistrationActivity::class.java))
    finish()
}

2. Use a Local Database (Room) for Complex User Data #

If your User class has more fields (like bio, profile picture URL, etc.), use Room to store the full user object. Combine this with SharedPreferences to track the logged-in user's ID.

Example Room Entity:

@Entity(tableName = "users")
data class User(
    @PrimaryKey val id: String,
    val email: String,
    val username: String,
    val bio: String? = null
)

Save User to Room After Registration:

// Assuming you have a Room DAO interface set up
userDao.insertUser(currentUser)
// Also save user ID to SharedPreferences as shown above

Load User from Room in Other Activities:

val userId = sharedPref.getString("user_id", null)
userId?.let {
    // Use coroutines or LiveData to fetch the user from Room safely
    lifecycleScope.launch {
        currentUser = userDao.getUserById(it)
    }
}

3. Use a Singleton Class for In-Memory Access #

Create a singleton to hold CurrentUser in memory for quick access, but always back it up with SharedPreferences/Room so it survives app restarts.

Example Singleton:

object UserSessionManager {
    var currentUser: User? = null

    fun saveUser(context: Context, user: User) {
        currentUser = user
        // Persist the user ID to SharedPreferences
        val sharedPref = context.getSharedPreferences("BlogAppSession", Context.MODE_PRIVATE)
        sharedPref.edit().putString("user_id", user.id).apply()
    }

    fun loadUser(context: Context, userDao: UserDao) {
        val sharedPref = context.getSharedPreferences("BlogAppSession", Context.MODE_PRIVATE)
        val userId = sharedPref.getString("user_id", null)
        userId?.let {
            // Fetch user from Room and initialize currentUser
            lifecycleScope.launch {
                currentUser = userDao.getUserById(it)
            }
        }
    }
}

Then, in your app's Application class, call UserSessionManager.loadUser(this, userDao) on startup to initialize currentUser right when the app launches.

Key Best Practices #

• Always Validate CurrentUser: Before using currentUser in any activity/fragment, check if it's null. If it is, redirect to the registration/login page.
• Clear Session on Logout: When the user logs out, delete the session data from SharedPreferences/Room and set currentUser to null.
• Avoid Intent Extras for User Data: Passing CurrentUser via Intent extras is inefficient and can break if the object is large or not parcelable. Use persistence instead.

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