Fix Android DNSSD signal 3 issue

joonhaengHeo · Sep 3, 2024 · 8c279fa · 8c279fa
1 parent daa2a57
commit 8c279fa
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/src/platform/android/java/chip/platform/NsdManagerServiceResolver.java b/src/platform/android/java/chip/platform/NsdManagerServiceResolver.java
@@ -27,6 +27,7 @@
 import java.util.ArrayList;
 import java.util.List;
 import java.util.concurrent.CopyOnWriteArrayList;
+import java.util.concurrent.ExecutorService;
 import java.util.concurrent.Executors;
 import java.util.concurrent.ScheduledFuture;
 import java.util.concurrent.TimeUnit;
@@ -45,6 +46,8 @@ public class NsdManagerServiceResolver implements ServiceResolver {
   @Nullable private final NsdManagerResolverAvailState nsdManagerResolverAvailState;
   private final long timeout;
 
+  private ExecutorService mResolveExecutorService;
+
   /**
    * @param context application context
    * @param nsdManagerResolverAvailState Passing NsdManagerResolverAvailState allows
@@ -69,6 +72,8 @@ public NsdManagerServiceResolver(
 
     this.nsdManagerResolverAvailState = nsdManagerResolverAvailState;
     this.timeout = timeout;
+
+    mResolveExecutorService = Executors.newSingleThreadExecutor();
   }
 
   public NsdManagerServiceResolver(Context context) {
@@ -116,7 +121,7 @@ public void run() {
           }
         };
 
-    new Thread(
+    mResolveExecutorService.execute(
             () -> {
               if (nsdManagerResolverAvailState != null) {
                 nsdManagerResolverAvailState.acquireResolver();
@@ -137,8 +142,7 @@ public void run() {
                       resolveTimeoutExecutor,
                       nsdManagerResolverAvailState);
               serviceFinderResolver.start();
-            })
-        .start();
+            });
   }
 
   @Override