Don't worry about ADB SIGKILL startup errors

Author: pimterry

src/interceptors/android/adb-commands.ts

@@ -61,6 +61,7 @@ export const getConnectedDevices = batchCalls(async (adbClient: adb.AdbClient) =
             e.code === 'ENOENT' || // No ADB available
             e.code === 'EACCES' || // ADB available, but we aren't allowed to run it
             e.code === 'ECONNREFUSED' || // Tried to start ADB, but still couldn't connect
+            e.signal === 'SIGKILL' || // In some envs 'adb start-server' is always killed (why?)
             (e.cmd && e.code)      // ADB available, but "adb start-server" failed
         ) {
             if (e.code !== 'ENOENT') {