IssueTracker

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...

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

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?

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?

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.

sh...@google.com

I don't have a way to upgrade my kernel version

he actually meant "upgrade macOS" because of "I can let you know I am on MacOS version 12.6.3 and am on a MacBook Pro (16-inch, 2019)" from earlier. we added this patch because people on macOS 13 seem to need it (and that's all we can test on, because Google requires us to be on the current version for security reasons!). so anecdotally ("lack of evidence") we think that this is probably macOS 12 vs 13 rather than arm64 vs intel, and think that should solve your problem?

thanks! (and apologies in advance in case we have more questions later as we try to work out what the active ingredient is here ... i'll keep my fingers crossed that it's just this :-) )

Do you want me to update to 34.0.1?

that would be an interesting datapoint, but that should be equivalent to 34.0.0 with ADB_OSX_USB_CLEAR_ENDPOINTS=1... (you remembered the adb kill-server dance, and remembered to use export?)