Files
apk-reverse/skills
inliver233 905544ea89 Name the three path namespaces, and where a crossing is legal
A path in this skill lives in one of three places -- the host filesystem, the device filesystem, or an
APK entry name -- and the same string means something different in each. Two properties decide most
of the failures that follow:

  * a host path does not exist on the device and vice versa; `adb push`/`adb pull` is the only place
    a translation happens, and it is the caller's to make;
  * an entry name is always `/`-separated and case-sensitive whatever the host OS is, so a path built
    with `os.path.join` matches nothing on Windows.

The symptom is a "no such file" naming a path you can see exists -- on the other side of the boundary.
`environment.md` now says to ask which namespace a string is in before asking whether the file is
there, and points at `validate_device_path`, which refuses a host-shaped path before it reaches the
device shell where it would fail far from the caller.

The leak scan caught the first draft: the example in the table was a real-looking POSIX home path and
`scan_leaks.py` flagged it as target identity. The scanner was right and the example was wrong; it now
uses a placeholder.
2026-10-16 19:23:59 +08:00
..