Android：重新联网时仅执行一次代码的实现方案问询

Great question! I’ve run into this exact issue before—CONNECTIVITY_CHANGE is tricky because it fires for both connection and disconnection events, which is why your code is running when you don’t want it to. Let’s walk through two solid solutions to fix this, including a modern approach that’s more reliable for newer Android versions.

Instead of running code every time the broadcast fires, first validate that the device actually has an active, usable network connection. Here’s how to adjust your existing implementation:

private BroadcastReceiver connectivityReceiver = new BroadcastReceiver() {
    @Override
    public void onReceive(Context context, Intent intent) {
        ConnectivityManager cm = (ConnectivityManager) context.getSystemService(Context.CONNECTIVITY_SERVICE);
        NetworkInfo activeNetwork = cm.getActiveNetworkInfo();
        
        // Only proceed if we have a connected/connecting network
        if (activeNetwork != null && activeNetwork.isConnectedOrConnecting()) {
            // Execute your one-time code here
            runYourSpecificTask();
            
            // Unregister immediately to prevent future triggers
            context.unregisterReceiver(this);
        }
    }
};

// Register the receiver (call this in onCreate() of your Activity/Fragment)
IntentFilter filter = new IntentFilter(ConnectivityManager.CONNECTIVITY_ACTION);
registerReceiver(connectivityReceiver, filter);

Important Notes for This Approach: #

• isConnectedOrConnecting() ensures we only react when a network becomes available, not when it’s lost.
• If you registered the receiver statically (in AndroidManifest.xml), you can’t dynamically unregister it—so stick to dynamic registration for this use case.

Starting with Android 7.0 (API 24), the CONNECTIVITY_ACTION broadcast has restrictions when your app is in the background. The official, more reliable alternative is NetworkCallback, which only triggers onAvailable() when a usable network is established—no need to filter out disconnection events manually.

private ConnectivityManager.NetworkCallback networkCallback = new ConnectivityManager.NetworkCallback() {
    @Override
    public void onAvailable(Network network) {
        super.onAvailable(network);
        // Run your one-time task
        runYourSpecificTask();
        
        // Unregister the callback right away to stop listening
        ConnectivityManager cm = (ConnectivityManager) getSystemService(Context.CONNECTIVITY_SERVICE);
        cm.unregisterNetworkCallback(this);
    }
};

// Register the callback (call this when you want to start listening for network recovery)
ConnectivityManager cm = (ConnectivityManager) getSystemService(Context.CONNECTIVITY_SERVICE);
NetworkRequest networkRequest = new NetworkRequest.Builder()
        .addCapability(NetworkCapabilities.NET_CAPABILITY_INTERNET)
        .addTransportType(NetworkCapabilities.TRANSPORT_WIFI)
        .addTransportType(NetworkCapabilities.TRANSPORT_CELLULAR)
        .build();
cm.registerNetworkCallback(networkRequest, networkCallback);

Why This Is Better: #

• onAvailable() only fires when a network with internet access is active—no false triggers from disconnections.
• It avoids background broadcast limitations in newer Android versions, making it more reliable for long-running or background use cases.

• Always unregister immediately after your task runs: This guarantees your code won’t execute again for subsequent network changes.
• Handle configuration changes: If your Activity/Fragment is recreated (e.g., screen rotation), you’ll need to re-register the receiver/callback if you still need to listen for network recovery.
• Avoid memory leaks: Make sure to unregister in onDestroy() (or onStop()) as a fallback, just in case your task doesn’t run (e.g., network never connects before the app closes).

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