无线文件共享App Socket跨设备连接失败问题排查求助

Hey there, let's break down why your devices aren't connecting and walk through actionable fixes you can try right away. I've tackled similar socket/Wi-Fi Direct connection problems before, so these are the most common pain points to check:

1. Verify Network & Group Owner Address (Critical for Wi-Fi Direct) #

If you're using Wi-Fi Direct for file sharing, double-check that groupOwnerAddress is correctly retrieved from the Wi-Fi P2P connection callback. It's easy to accidentally pass the wrong device's address here—make sure you're using the address of the device running the ServerSocket (the group owner).

2. Check Permissions (Don't Skip This!) #

Android requires specific permissions for network operations, especially for Wi-Fi Direct:

• Add these to your AndroidManifest.xml:

  <uses-permission android:name="android.permission.INTERNET"/>
  <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
  <uses-permission android:name="android.permission.CHANGE_WIFI_STATE"/>
  <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/> <!-- Required for Wi-Fi Direct on Android 6+ -->
  

• For Android 6 and above, you'll need to request the ACCESS_FINE_LOCATION permission dynamically at runtime—Wi-Fi Direct won't work without it.

3. Fix Connection Order & Timing #

You must start the receiving AsyncTask (with ServerSocket) first before initiating the send request. If the sender tries to connect before the receiver's ServerSocket is listening, you'll get a "connection refused" error. Add a clear user flow (e.g., prompt the user to tap "Receive" first, then "Send") to enforce this order.

4. Add Timeouts & Error Logging #

Your current code lacks timeout handling and error logging, which makes debugging impossible. Update your socket code to:

• Add a connection timeout to the sender's connect() call (prevents hanging indefinitely):

  client.connect(new InetSocketAddress(groupOwnerAddress, 8888), 5000); // 5-second timeout
  

• Wrap all socket operations in try-catch blocks and log detailed errors:

  catch (IOException e) {
      Log.e("SocketDebug", "Connection failed: " + e.getMessage());
      // Show an error message to the user here
  }
  

  The error message will tell you exactly what's wrong—whether it's a timeout, refused connection, or port conflict.

5. Handle AsyncTask Lifecycle & Resource Cleanup #

AsyncTasks are tied to the Activity lifecycle, so if your Activity is destroyed (e.g., screen rotation), the AsyncTask will be canceled, leaving sockets open. Fix this by:

• Canceling the AsyncTask in your Activity's onDestroy() method:

  @Override
  protected void onDestroy() {
      super.onDestroy();
      if (receiveTask != null && receiveTask.getStatus() != AsyncTask.Status.FINISHED) {
          receiveTask.cancel(true);
      }
      // Do the same for sendTask
  }
  

• Always close sockets in a finally block to avoid port leaks:

  finally {
      try {
          if (client != null) client.close();
          if (server != null) server.close();
      } catch (IOException e) {
          e.printStackTrace();
      }
  }
  

6. Check for Port Conflicts #

Port 8888 might be used by another app on either device. Try switching to a less common port (e.g., 10240) to rule out conflicts.

Quick Validation Test #

1. Ensure both devices are on the same Wi-Fi network (or have an active Wi-Fi Direct connection).
2. Start the receiver AsyncTask first—check Logcat for "Waiting for connection..." to confirm the ServerSocket is listening.
3. Start the sender AsyncTask and watch Logcat for connection errors or success messages.

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