allow usb debugging dialog in api 30 android emulator system image closed [198549504]

Can't Repro

Bug

Status Update

No update yet.

Description

ho...@gmail.com

created issue #1

Sep 2, 2021 01:30PM

STEPS TO REPRODUCE:

open avd manager and start an api 30 android emulator
open Troubleshoot device connection
restart adb server and see the dialog opend after a moment and reclosed Instantly

2021-09-02 17:55:27,385 [2617412]   INFO -            #com.android.ddmlib - Connected to adb for device monitoring 
2021-09-02 17:55:27,427 [2617454]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:27,435 [2617462]   INFO - roid.tools.idea.adb.AdbService - ADB connection successfully terminated 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,274 [2619301]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:29,574 [2619601]   WARN -            #com.android.ddmlib - * daemon not running; starting now at tcp:5037 
2021-09-02 17:55:29,615 [2619642]   WARN -            #com.android.ddmlib - * daemon started successfully 
2021-09-02 17:55:29,644 [2619671]   INFO -            #com.android.ddmlib - Connected to adb for device monitoring 
2021-09-02 17:55:29,846 [2619873]   INFO - manager.EmulatorProcessHandler - Emulator: emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037 
2021-09-02 17:55:29,890 [2619917]   INFO - roid.tools.idea.adb.AdbService - Successfully connected to adb 
2021-09-02 17:55:30,278 [2620305]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:30,278 [2620305]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:30,279 [2620306]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:30,280 [2620307]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:30,285 [2620312]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:31,491 [2621518]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:32,504 [2622531]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:36,929 [2626956]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,929 [2626956]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,929 [2626956]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,930 [2626957]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,930 [2626957]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,930 [2626957]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:36,930 [2626957]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:37,385 [2627412]   INFO - roid.tools.idea.adb.AdbService - Cancelling current future since it finished with a failure 
2021-09-02 17:55:37,386 [2627413]   INFO - roid.tools.idea.adb.AdbService - Initializing adb using: D:\Android SDK\platform-tools\adb.exe 
2021-09-02 17:55:37,386 [2627413]   INFO - roid.tools.idea.adb.AdbService - Terminating ADB connection 
2021-09-02 17:55:39,009 [2629036]   WARN -            #com.android.ddmlib - * daemon not running; starting now at tcp:5037 
2021-09-02 17:55:39,049 [2629076]   WARN -            #com.android.ddmlib - * daemon started successfully 
2021-09-02 17:55:39,062 [2629089]   INFO -            #com.android.ddmlib - Connected to adb for device monitoring 
2021-09-02 17:55:39,108 [2629135]   WARN -            #com.android.ddmlib - Adb connection Error:An existing connection was forcibly closed by the remote host 
2021-09-02 17:55:39,122 [2629149]   INFO - roid.tools.idea.adb.AdbService - ADB connection successfully terminated 
2021-09-02 17:55:40,977 [2631004]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,978 [2631005]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,978 [2631005]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,978 [2631005]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,977 [2631004]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,978 [2631005]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:40,978 [2631005]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:41,258 [2631285]   WARN -            #com.android.ddmlib - * daemon not running; starting now at tcp:5037 
2021-09-02 17:55:41,289 [2631316]   WARN -            #com.android.ddmlib - * daemon started successfully 
2021-09-02 17:55:41,302 [2631329]   INFO -            #com.android.ddmlib - Connected to adb for device monitoring 
2021-09-02 17:55:41,509 [2631536]   INFO - roid.tools.idea.adb.AdbService - Successfully connected to adb 
2021-09-02 17:55:41,981 [2632008]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:41,981 [2632008]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:41,981 [2632008]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:41,981 [2632008]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:41,982 [2632009]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:41,982 [2632009]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds. 
2021-09-02 17:55:43,155 [2633182]   WARN -            #com.android.ddmlib - Cannot reach ADB server, attempting to reconnect. 
2021-09-02 17:55:44,170 [2634197]   INFO -            #com.android.ddmlib - ADB connection re-established after 1 seconds.

Stackoverflow :

after some testing I found that Pixel 4 API 30 have your problem

Studio Build: arctic fox 2020.3.1

Version of Gradle Plugin: 7.0.1

Version of Gradle: 7.2

Version of Java: 11

OS: Windows 10 pro

Comments

ho...@gmail.com <ho...@gmail.com> #2Sep 2, 2021 04:48PM

+1 to this feature request, came here seeking help at

https://serverfault.com/questions/987908/custom-routes-rejected-by-gke-peer-configuration/988167#988167
We will to build CD pipelines with agents running in internal on-premise network, peered with GCP network. GKE private endpoint is not reachable in this case.

sr...@google.com <sr...@google.com> Sep 2, 2021 06:05PM

Assigned to an...@google.com.

ho...@gmail.com <ho...@gmail.com> #3Sep 10, 2021 07:29AM

+1 Could be quite a useful feature for us.
Ideally, we don't want to have public IP for K8S API at all and manage it privately inside the org with a hybrid architecture site-2-site VPN etc.

Message last modified on Sep 23, 2021 05:46AM

ju...@google.com <ju...@google.com> Dec 1, 2021 07:10PM

Status: New

zs...@google.com <zs...@google.com> #4Mar 26, 2025 04:42PM

Status: Won't Fix (Not Reproducible)

I thought this would be resolved now that the VPC Peerings of private GKE will accept routes exported from the VPC. But it still doesn't seem to work for me.