From 4ab88eb5729ff95460e59876daa23cc0fa68ed29 Mon Sep 17 00:00:00 2001 From: Eric House Date: Sat, 20 Aug 2022 09:55:59 -0700 Subject: [PATCH] revert test for connectedness in mqtt shutdown An assertion's firing indicating I don't understand what's going on. Let's study some more first. --- .../java/org/eehouse/android/xw4/MQTTUtils.java | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/xwords4/android/app/src/main/java/org/eehouse/android/xw4/MQTTUtils.java b/xwords4/android/app/src/main/java/org/eehouse/android/xw4/MQTTUtils.java index 6917f5e46..3eac7cd66 100644 --- a/xwords4/android/app/src/main/java/org/eehouse/android/xw4/MQTTUtils.java +++ b/xwords4/android/app/src/main/java/org/eehouse/android/xw4/MQTTUtils.java @@ -489,22 +489,16 @@ public class MQTTUtils extends Thread String action = null; IMqttToken token = null; try { - boolean isConnected = client.isConnected(); switch ( ii ) { case 0: - if ( isConnected ) { - action = "unsubscribe"; - token = client.unsubscribe( mTopics ); - } + action = "unsubscribe"; + token = client.unsubscribe( mTopics ); break; // not continue, which skips the Log() below case 1: - if ( isConnected ) { - action = "disconnect"; - token = client.disconnect(); - } + action = "disconnect"; + token = client.disconnect(); break; case 2: - Assert.assertTrueNR( !isConnected ); action = "close"; client.close(); break;