Android中Firebase连接状态（在线/离线）检测及用户显示逻辑求助

Hey there, let's tackle this problem step by step—we'll cover syncing offline status to Firebase and handling both of your required search scenarios, plus add safeguards for edge cases like unexpected app crashes or device shutdowns.

1. Core: Sync Network Status to Firebase connections Node #

First, we need to reliably update the connections node whenever the user's network state changes. We'll combine device-level network monitoring with Firebase's built-in onDisconnect method to cover both intentional and unexpected offline events.

Device Network Monitoring (Android Example) #

Use the ConnectivityManager to listen for network state changes and update Firebase in real-time:

val connectivityManager = getSystemService(Context.CONNECTIVITY_SERVICE) as ConnectivityManager
val networkCallback = object : ConnectivityManager.NetworkCallback() {
    override fun onAvailable(network: Network) {
        super.onAvailable(network)
        // Network restored: mark user as online
        FirebaseDatabase.getInstance().reference.child("connections")
            .child(currentUserId) // Replace with your user's unique ID
            .setValue(true)
    }

    override fun onLost(network: Network) {
        super.onLost(network)
        // Network disconnected: mark user as offline
        FirebaseDatabase.getInstance().reference.child("connections")
            .child(currentUserId)
            .setValue(false)
    }
}

// Register the network listener
connectivityManager.registerDefaultNetworkCallback(networkCallback)

Device Network Monitoring (iOS Example) #

Use NWPathMonitor to track network status on iOS:

let networkMonitor = NWPathMonitor()
networkMonitor.pathUpdateHandler = { path in
    let isConnected = path.status == .satisfied
    // Update Firebase with current connection status
    Database.database().reference().child("connections")
        .child(currentUserId) // Replace with your user's unique ID
        .setValue(isConnected)
}

let monitorQueue = DispatchQueue(label: "NetworkStatusQueue")
networkMonitor.start(queue: monitorQueue)

Critical Safeguard: Firebase onDisconnect #

To handle cases where the app crashes or the device shuts down abruptly (network monitoring won't trigger here), use Firebase's onDisconnect method. This tells Firebase to automatically set the connections node to false if the server detects the client has disconnected:

// Initialize on app start: set user as online, and schedule offline status on disconnect
val userConnectionRef = FirebaseDatabase.getInstance().reference.child("connections").child(currentUserId)
userConnectionRef.onDisconnect().setValue(false)
userConnectionRef.setValue(true)

2. Handle Your Two Search Scenarios #

Scenario 1: Offline Users Don't Appear in Initial Search Results #

Modify your Firebase query to filter only users where connections is true. This ensures offline users are excluded from the initial search list:

// Query only online users
FirebaseDatabase.getInstance().reference.child("users")
    .orderByChild("connections") // Assume your users node has a connections child, or join with the connections node
    .equalTo(true)
    .addValueEventListener(object : ValueEventListener {
        override fun onDataChange(snapshot: DataSnapshot) {
            // Populate your search results list with only online users
            val onlineUsers = snapshot.children.map { it.getValue(User::class.java) }
            updateSearchResultsUI(onlineUsers)
        }

        override fun onCancelled(error: DatabaseError) {
            // Handle query error
        }
    })

Note: If your users and connections nodes are separate, you can structure the query to join them by user ID, or denormalize the connections status into the users node for simpler queries.

Scenario 2: Show "NO MORE AVAILABLE" Icon When a User Goes Offline Mid-Search #

After loading the initial search results, add a real-time listener to each user's connections node. This lets you update the UI immediately when a user goes offline:

// After fetching initial search results
for (userSnapshot in snapshot.children) {
    val userId = userSnapshot.key ?: continue
    val user = userSnapshot.getValue(User::class.java) ?: continue

    // Add listener to track this user's connection status
    FirebaseDatabase.getInstance().reference.child("connections").child(userId)
        .addValueEventListener(object : ValueEventListener {
            override fun onDataChange(statusSnapshot: DataSnapshot) {
                val isAvailable = statusSnapshot.getValue(Boolean::class.java) ?: false
                // Update UI: show/hide offline icon based on status
                if (!isAvailable) {
                    showOfflineIconForUser(userId) // Your UI method to display "NO MORE AVAILABLE"
                } else {
                    hideOfflineIconForUser(userId)
                }
            }

            override fun onCancelled(error: DatabaseError) {
                // Handle listener error
            }
        })
}

Pro Tip: Don't forget to remove these listeners when the user navigates away from the search screen to avoid memory leaks.

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