LiveData首次调用后无法触发观察者回调问题求助

Hey there! I’ve dealt with similar LiveData + FileObserver issues before, so let’s break down why your callback isn’t firing after deleting a file, and how to fix it.

Common Culprits & Fixes #

1. You’re Reusing the Same List Instance (LiveData Ignores Reference-Matching Updates) #

This is the most frequent issue. LiveData only triggers onChange when the reference of the data changes—not just when the content inside the object changes.

If you’re modifying an existing List (e.g., removing an element) and calling setValue() with that same list, LiveData will see the old and new references as identical and skip the notification.

Fix: Create a brand new List every time you load file names:

private val _fileNamesLiveData = MutableLiveData<List<String>>()
val fileNamesLiveData: LiveData<List<String>> = _fileNamesLiveData

private fun loadFileNames() {
    val cameraDir = File(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DCIM), "Camera")
    val newFileList = cameraDir.listFiles()?.map { it.name } ?: emptyList()
    _fileNamesLiveData.setValue(newFileList) // New List instance every time
}

2. FileObserver Callback Runs on a Non-Main Thread (setValue Requires Main Thread) #

FileObserver’s onEvent method executes on a Binder background thread, not the main thread. LiveData’s setValue() must be called from the main thread—if you call it from a background thread, it won’t trigger the observer and may even throw an exception.

Fix: Switch to the main thread before updating LiveData, or use postValue() instead:

class CameraFileObserver(path: String) : FileObserver(path, FileObserver.DELETE) {
    override fun onEvent(event: Int, path: String?) {
        if (event == FileObserver.DELETE) {
            // Option 1: Use Handler to post to main thread
            Handler(Looper.getMainLooper()).post {
                loadFileNames() // This calls setValue on main thread
            }
            
            // Option 2: Use postValue directly (works from any thread)
            // val newFileList = getUpdatedFileList()
            // _fileNamesLiveData.postValue(newFileList)
        }
    }
}

3. FileObserver Isn’t Configured Correctly #

Double-check that your FileObserver is actually detecting the deletion event:

• Make sure you called startWatching() after creating the observer (easy to forget!);
• Verify the event mask includes FileObserver.DELETE (or FileObserver.ALL_EVENTS for testing);
• Confirm the target path is correct—use Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DCIM).resolve("Camera") to avoid hardcoding errors;
• Ensure your app has the necessary storage permissions (READ_EXTERNAL_STORAGE for Android 9 and below, or use MediaStore/MANAGE_EXTERNAL_STORAGE for Android 10+).

4. LifecycleOwner Is Inactive #

LiveData only delivers updates to observers when their associated LifecycleOwner (e.g., Activity/Fragment) is in an active state (resumed or started). If you delete the file while the app is in the background (e.g., Activity is paused), LiveData will cache the update and deliver it only when the app returns to the foreground.

Check: Add logs in your observer’s onChange method to see if the update comes through once you bring the app back to focus.

5. ViewModel Instance Is Recreated Accidentally #

If you’re creating a new ViewModel instance instead of reusing the existing one, your observer will be subscribed to an old LiveData instance—meaning updates from the new ViewModel won’t reach it.

Fix: Always get your ViewModel via ViewModelProvider to ensure a single instance is used:

// In your Activity/Fragment
val viewModel = ViewModelProvider(this)[CameraViewModel::class.java]
viewModel.fileNamesLiveData.observe(this) { fileNames ->
    // Update UI
}

Quick Debugging Steps #

1. Add logs in loadFileNames() to confirm it’s being called after deletion, and that the new file list is different from the old one.
2. Check logcat for exceptions related to LiveData thread violations.
3. Verify the LiveData instance in your observer is the same one being updated in the ViewModel.

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