Android应用向MQTT Broker发布消息时崩溃问题求助

Hey there! Let's work through this crash issue—since your app runs fine without the MQTT code, the problem is almost certainly tied to how you're setting up or using the MQTT client. Here are the most common fixes to check:

1. Double-Check Permissions & Service Registration #

Android requires explicit permissions for network access, and the Eclipse Paho MQTT library (the most common for Android) needs a background service to function properly.

First, add these permissions to your AndroidManifest.xml:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<!-- For Android 10+, add this if you need MQTT to work in the background -->
<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />

Then register the Paho MQTT service inside the <application> tag of your manifest:

<service android:name="org.eclipse.paho.android.service.MqttService" />

2. Verify MQTT Dependencies Are Correct #

Make sure you're using compatible versions of the Paho libraries in your app-level build.gradle (or build.gradle.kts):

Groovy Syntax: #

dependencies {
    implementation 'org.eclipse.paho:org.eclipse.paho.client.mqttv3:1.2.5'
    implementation 'org.eclipse.paho:org.eclipse.paho.android.service:1.1.1'
}

Kotlin DSL Syntax: #

dependencies {
    implementation("org.eclipse.paho:org.eclipse.paho.client.mqttv3:1.2.5")
    implementation("org.eclipse.paho:org.eclipse.paho.android.service:1.1.1")
}

3. Never Run MQTT Operations on the Main Thread #

Android blocks network calls on the main thread (to keep the UI responsive), so if you're connecting or publishing messages directly from your switch's click listener, that's almost certainly causing a crash.

Fix for Kotlin (Using Coroutines): #

Use lifecycleScope to run MQTT code on an IO thread:

yourSwitch.setOnCheckedChangeListener { _, isChecked ->
    lifecycleScope.launch(Dispatchers.IO) {
        // Use a unique client ID to avoid connection conflicts
        val mqttClient = MqttAndroidClient(applicationContext, "tcp://YOUR_RPI_IP:1883", "android_${System.currentTimeMillis()}")
        val options = MqttConnectOptions().apply {
            isCleanSession = true
            // Uncomment if your Raspberry Pi broker requires authentication
            // userName = "your_mqtt_username"
            // password = "your_mqtt_password".toCharArray()
        }

        try {
            mqttClient.connect(options, null, object : IMqttActionListener {
                override fun onSuccess(token: IMqttToken?) {
                    val payload = if (isChecked) "on" else "off"
                    val message = MqttMessage(payload.toByteArray())
                    message.qos = 1 // QoS 1 ensures message delivery
                    mqttClient.publish("rpi/gpio", message)
                }

                override fun onFailure(token: IMqttToken?, exception: Throwable?) {
                    exception?.printStackTrace()
                    // Show user feedback (must run on main thread)
                    runOnUiThread {
                        Toast.makeText(applicationContext, "MQTT Connection Failed", Toast.LENGTH_SHORT).show()
                    }
                }
            })
        } catch (e: MqttException) {
            e.printStackTrace()
        }
    }
}

Fix for Java (Using Thread): #

Wrap your MQTT code in a background thread:

yourSwitch.setOnCheckedChangeListener((buttonView, isChecked) -> {
    new Thread(() -> {
        try {
            // Unique client ID to prevent connection clashes
            MqttAndroidClient client = new MqttAndroidClient(getApplicationContext(), "tcp://YOUR_RPI_IP:1883", "android_" + System.currentTimeMillis());
            MqttConnectOptions options = new MqttConnectOptions();
            options.setCleanSession(true);
            // Add auth if your broker requires it
            // options.setUserName("your_mqtt_username");
            // options.setPassword("your_mqtt_password".toCharArray());

            client.connect(options, null, new IMqttActionListener() {
                @Override
                public void onSuccess(IMqttToken asyncActionToken) {
                    String payload = isChecked ? "on" : "off";
                    MqttMessage message = new MqttMessage(payload.getBytes());
                    message.setQos(1);
                    try {
                        client.publish("rpi/gpio", message);
                    } catch (MqttException e) {
                        e.printStackTrace();
                    }
                }

                @Override
                public void onFailure(IMqttToken asyncActionToken, Throwable exception) {
                    exception.printStackTrace();
                    runOnUiThread(() -> Toast.makeText(getApplicationContext(), "MQTT Connection Failed", Toast.LENGTH_SHORT).show());
                }
            });
        } catch (MqttException e) {
            e.printStackTrace();
        }
    }).start();
});

4. Use a Unique Client ID #

Every MQTT client connecting to your Raspberry Pi broker needs a unique ID. Reusing IDs can cause unexpected disconnections or crashes. Using a timestamp (like android_${System.currentTimeMillis()}) ensures each connection has a unique identifier.

5. Check Crash Logs for Exact Errors #

If you're still stuck, open Android Studio's Logcat and filter for "Error" or "Exception" to see the exact crash cause. Common issues include:

• NetworkOnMainThreadException: You're running MQTT operations on the main thread (fix with the thread/coroutine code above)
• MqttException with error code 3: Broker connection failed (verify your RPi IP, ensure port 1883 is open, and confirm the MQTT broker is running on the Pi)
• SecurityException: Missing permissions (fix with the manifest permissions listed earlier)

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