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

you explicitly mention "brew", which is nothing to do with us, but imply that when you downloaded "platform tools" (presumably from developer.google.com), that worked. so i think you need to talk to the (home?)brew folks...

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

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

No by brew I meant that my platform tools recently updated. I ran brew through an update and as a part of the update it updates all the packages you've installed using brew, and android platfrom tools is one of them. Brew doesn't let you downgrade platform tools version, and neither does the Android website. But I found the previous version of platform tools on another website and uninstalled the 34.0 version and used the 33.0.3 and it was working. So no I wasn't implying that brew broke it, I shouldn't have even included brew in my explanation, just explaining that I recently updated the platform tools and that's when this issue came up.

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

In fact, I just installed the latest Android Platform Tools from

https://developer.android.com/studio/releases/platform-tools and it has the same issue.

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

did you adb kill-server to ensure you're actually running the new one?

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

I forgot to mention I am on Mac.

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

Yes I did that.

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

Are you not gonna fix it even though it was working in the 33.0.3 release?

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

Are you not gonna fix it even though it was working in the 33.0.3 release?

at the moment, this is at best on the "maybe there's the a problem?" pile. if macOS was as broken as you suggest, we'd probably have heard more than one complaint by now. so in the meantime, there are lots of other more bugs to look at, that we're already convinced are real.

you can make this bug more convincing by trying to work out what the actual variable is --- is it some specific model of mac? is it only some specific macOS versions? android versions? is there anything interesting in logcat?

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

If you want to know specific Mac's and MacOS versions it's broken on, I don't have any time for that, nor do I have the equipment for that, I have one Macbook. I can let you know I am on MacOS version 12.6.3 and am on a MacBook Pro (16-inch, 2019). As far as it being broken on other platforms, I may have time to test on Windows and seem if the platform tools on Windows has the same issue in the latest version. And I don't know how logcat would show any issues if the adb shell command is working just fine over USB, it's just the install function that isn't working and is hanging. I haven't tested all the adb functions nor do I use them all, so no I wasn't suggesting all of ADB was broken on Mac either. I specifically mentioned the adb install command.

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

Also the fact that it was working in the previous platform tools release, and then you assuming that I would make a bug up just because is pretty far out there. It was working and I just noticed it because platform tools was recently updated. As far as specific Android versions, so far I have tested on Android 7 and Android 9 and it still works on Android 7 but does not work on Android 9. Those are the two main Android versions I work on so as far as other Android versions it working or not, I don't know.

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

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

Also the fact that it was working in the previous platform tools release, and then you assuming that I would make a bug up just because is pretty far out there.

not make it up, just be confused/mistaken. you'd be surprised how many of our bug reports are "user error" or "bad cable". is anyone else on your team having similar troubles? have you tried --no-streaming to confirm it's specifically the streaming?

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

Assigned to de...@google.com.

Yeah I get that. I tried multiple USB cables too and multiple tablets on Android 9 and still got the same issue. And I tried on the Windows platfrom tools and adb there doesn't have the same issue. As far as anyone else on my team having the same issue, I'm not sure because they don't really update their platform tools. They are on older versions. I also just tried the no-streaming option and it was still having the same hang issue, just get's stuck on performing push install instead.

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

Marked as fixed.

does export ADB_OSX_USB_CLEAR_ENDPOINTS=1 (https://android-review.googlesource.com/c/platform/packages/modules/adb/+/2323082) help? you'll need to restart the server with that in your environment to test.

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