You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(android): warn about cmdline-tools double-nesting + force fresh shell
The "extract to cmdline-tools/latest/" instruction was too easy to
misread as "drag the cmdline-tools folder into latest/", which produces
a doubly-nested cmdline-tools/latest/cmdline-tools/bin/ that sdkmanager
can't find from PATH. Adds the exact target layout, a fix-in-place
snippet for people who already hit it, and a "close every Powershell"
nudge so env vars are actually live.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/dev/android-build-handover.md
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,16 +56,43 @@ java -version # should show "openjdk version 17.x.x"
56
56
### Install Android command-line tools
57
57
58
58
1. Download from `https://developer.android.com/studio#command-line-tools-only` — the "Command line tools only" zip (Windows).
59
-
2. Extract to `C:\android-sdk\cmdline-tools\latest\` (note: the `latest` folder is required by Google's installer paths).
59
+
2. Extract somewhere temporary first — the zip contains a single `cmdline-tools/` folder. You need to end up with this **exact** layout (Google's hard-coded convention):
60
+
61
+
```
62
+
C:\android-sdk\
63
+
cmdline-tools\
64
+
latest\
65
+
bin\
66
+
sdkmanager.bat
67
+
avdmanager.bat
68
+
lib\
69
+
NOTICE.txt
70
+
source.properties
71
+
```
72
+
73
+
The most common mistake is dragging the whole `cmdline-tools/` folder into `latest/`, which gives you `C:\android-sdk\cmdline-tools\latest\cmdline-tools\bin\...` — one level too deep. `sdkmanager.bat` must be at `cmdline-tools\latest\bin\sdkmanager.bat` exactly.
0 commit comments