Android Emulator 33.1.23 `-http-proxy` switch is parsed incorrectly [314614435]

Fixed

Bug

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Dec 4, 2023 11:02AM

DESCRIBE THE ISSUE IN DETAIL: The -http-proxy command line parameter is not parsed correctly no matter what format I use - it uses an empty string as a hostname/ip and fails to connect. The port is parsed correctly. Formats I tried:

127.0.0.1:8888
http://127.0.0.1:8888
localhost:8888
1.2.3.4:8080

STEPS TO REPRODUCE:

emulator.exe -avd Pixel_3a_API_34_extension_level_7_x86_64 -http-proxy 127.0.0.1:8888 -verbose -debug-proxy
Check the console log
See the lines:

DEBUG   | setting up http proxy: proxy= port=8888
server name '' resolved to 10.13.13.5:8888
WARNING | Could not connect to proxy at :8888: timed out !
WARNING | Proxy will be ignored !

Studio Build: Android Studio Hedgehog | 2023.1.1; Build #AI-231.9392.1.2311.11076708, built on November 9, 2023
Android emulator version: 33.1.23.0 (build_id 11150993) (CL:N/A)
OS: Windows 11

Note: I tried to create the issue in "Android Studio > Emulator" component but got "You do not have permission to create issues in this component."

Comments

vs...@google.com <vs...@google.com> Dec 4, 2023 03:49PM

Assigned to an...@google.com.

rk...@google.com <rk...@google.com> Dec 4, 2023 06:11PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> Dec 4, 2023 07:53PM

Accepted by wd...@google.com.

ru...@gmail.com <ru...@gmail.com> #2Dec 15, 2023 04:09PM

Message last modified on Dec 15, 2023 04:11PM

ru...@gmail.com <ru...@gmail.com> #3Dec 20, 2023 12:24PM

lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.

ru...@gmail.com <ru...@gmail.com> #4Dec 20, 2023 03:13PM

@3 Why does it occur?
And why only from specific API of Android?
On API 28 for example, it doesn't occur...

Please fix this issue for all API versions of the emulator.

ru...@gmail.com <ru...@gmail.com> #5Jan 5, 2024 02:05PM

Another similar issue that's related https://b.corp.google.com/issues/226426377

ru...@gmail.com <ru...@gmail.com> #6Feb 19, 2024 10:20AM

RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.

al...@gmail.com <al...@gmail.com> #7Feb 20, 2024 06:33PM

@6 There are plenty of issues on emulator API 31 (and on Android 13 emulator). Many glitches. Spend 5 minutes on it and you will notice.
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...

kc...@gmail.com <kc...@gmail.com> #8Feb 26, 2024 08:37PM

@6 Also please check on all versions of the emulator, to see when this issue started, and fix from there.

wd...@google.com <wd...@google.com> #9Feb 27, 2024 03:53PM

I reproduced this bug on Windows with emulator version 31.2.10-8420304

ru...@gmail.com <ru...@gmail.com> #10Feb 27, 2024 04:00PM

@9 Please test on more API versions.

wd...@google.com <wd...@google.com> #11Feb 28, 2024 04:42PM

Found the root cause when the "call device" button was unresponsive. It became unresponsive because the inbound call failed to initialize. Basically, the modem simulator's shared FD failed. When receive_inbound_call is invoked, it is supposed to make connection to the "host server" via a shared fd but it is flaky on Windows unfortunately.

modem-simulator: receive_inbound_call:101 inbound call from 6505551212
modem-simulator: process_msgs:296 waiting for new messages ...
modem-simulator: main_host_thread:501 got connection at host server at 65094
modem-simulator: start_calling_thread:254 making a connection to main host server 65094
modem-simulator: main_host_thread:507 Detected close from the other side
modem-simulator: start_calling_thread:262 nothing read quit
modem-simulator: main_host_thread:494 looping at main host server at 65094
modem-simulator: start_calling_thread:284 done with this thread

Message last modified on Feb 28, 2024 04:51PM

bo...@google.com <bo...@google.com> #12Mar 13, 2024 06:41PM

@5 I can't reach the link you've provided.

@11 So it could be the same reason that this bug occurs:

https://issuetracker.google.com/issues/233123301
?

bo...@google.com <bo...@google.com> #13Mar 20, 2024 06:41PM

Assigned to de...@google.com.

RE#12 I have uploaded a patch to fix this issue. I don't think it's the same reason for https://issuetracker.google.com/issues/233123301

de...@google.com <de...@google.com> #14Apr 1, 2024 06:09PM

Marked as fixed.

@13 OK thanks.
Have you tested it on all API versions, to make sure that it doesn't cause new issues, and also fixes the issue on other places in case it's there too?

Message last modified on Apr 1, 2024 06:09PM