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

The CL is merged. This option will be available in the next canary release.

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

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

Which version? I don't see an option in 33.1.2

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

It's gonna be available since 33.1.4. The CL is merged after the build 9654821 which is 33.1.3.

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

Thanks!

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

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Emulator 33.1.4

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

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

Thnx

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

Gracias

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

I have confirmed that the issue is only happening on gfxstream due to some mingw build issue. https://android-review.git.corp.google.com/c/platform/external/qemu/+/1190020/24

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

Since the review link is not public, could you confirm that removing the ifdef is a legitimate fix (and the random rare crashes we we are seeing with removing the ifdef and building with gfxstream is something else) or are there other changes that need to be done?

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

RE#10 Thank you for pointing that out. Removing the ifdef is a legitmate fix. The random crash is interesting but I doubt it has to with removing ifdef. Previously the ifdef guard was there probably because we used to have migw windows target but I don't think it's there anymore.

My fix is landed in CL and the next canary and release branch will include the fix.

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

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

we will release update with the fix in 34.1.x stable soon

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

Assigned to de...@google.com.

Devki,
we need a new release for 34.1.x

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

Marked as fixed.

Emulator 34.1.20 has been released with a fix for this

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