adb push error about scrcpy HOT 9 CLOSED

it does not on my Debian

TIL. I just tried this out on Debian and I'm getting the same result as you. It looks like this is because Debian uses its own implementation of which while Arch uses which from coreutils.

from scrcpy.

Currently, it does not work over adb connect.

What if you use it over usb instead?

from scrcpy.

exec: No such file or directory

Are you sure that adb is in PATH?

from scrcpy.

More specifically, the issue causing is that exec expects your PATH to be fully expanded. Apparently, tilde expansion is a feature of the shell.

Here are two workarounds that work for me:

• Manually expand the tildes in your PATH: PATH="$PATH:$HOME/Android/Sdk/platform-tools" scrcpy
• Set the ADB environment variable before calling scrcpy: ADB=$(which adb) scrcpy

from scrcpy.

Apparently, tilde expansion is a feature of the shell.

Absolutely.

Manually expand the tildes in your PATH

Yes, that's a requirement.

Set the ADB environment variable before calling scrcpy: ADB=$(which adb) scrcpy

I think this should not change anything: if which adb gives a result, then it's in PATH, so scrcpy would find it.

from scrcpy.

On my machine (whose PATH contains "~/Android/Sdk/platform-tools") scrcpy does not work but ADB=$(which adb) scrpy does. I think this is because exec doesn't do tilde expansion, while which does.

from scrcpy.

OK, that's weird. On my Debian, I have the reverse behavior:

mkdir z
echo 'echo ok' > z/blabla
chmod +x z/blabla
export PATH="~/z:$PATH"

$ which blabla
$ blabla
ok

from scrcpy.

Yeah - my point is that which will implicitly do the tilde expansion as expected, but calls to execvp (like this one in scrcpy) do not.

from scrcpy.

Yeah - my point is that which will implicitly do the tilde expansion

Yes, but this surprises me.

as expected

IMO which should not expand ~ in PATH (and it does not on my Debian, cf my previous message, since blabla is not found) for consistency, since exec does not expand it.

from scrcpy.