Clarify skip installation
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
Steps to reproduce
- Fresh install from skip on Mac (follow https://skip.dev/docs/gettingstarted/ from 2026-02-24) with step 7 left out, because virtual device was already created in Android Studio
- check in CLI "skip android emulator list" for running devices (which was ok for me after adding ANDROID_SDK_PATH to PATH)
- Open Xcode
- Run build
- Receive error message with failed build
Actual results
Xcode build error with following messages:
Execution failed for task ':app:checkDevices'
Process 'command 'adb'' finished with exit value -1 (state: FAILED)
After long hours of research I stumbled over installing https://skip.dev/docs/app-development/#running-on-device where /opt/homebrew/bin/adb is used from homebrew which I added to PATH from Android Studio. When I installed android-platform-tools from homebrew the build finish successfully.
But I could not run the build either, because I had to manually start the Android virtual device before running the build process.
Logs
No response
Skip Checkup output
[✓] Skip version 1.7.2 (= 1.7.2)
[✓] macOS version 26.3 (> 13.5.0)
[✓] macOS architecture: ARM
[✓] Swift version 6.2.3 (> 5.9.0)
[✓] Swiftly version 1.1.1 (> 1.0.0)
[✓] Xcode version 26.2 (> 15.0.0)
[✓] Xcode tools SDKs: 5
[✓] Homebrew version 5.0.15 (> 4.1.0)
[✓] Gradle version 9.3.1 (> 8.6.0)
[✓] Java version 21.0.9 (> 17.0.0)
[✓] Android Debug Bridge version 1.0.41 (> 1.0.40)
[✓] Android SDK version 36.0.2 (> 29.0.0)
[✓] Resolve dependencies (9.21s)
[✓] Build hello-skip (13.59s)
[✓] Test Swift (8.49s)
[✓] Test Kotlin (30.83s)
[✓] Check project schemes (6.49s)
[✓] Archive iOS ipa (7.76s)
[✓] Assemble HelloSkip-debug.ipa 175 KB
[✓] Verifying HelloSkip-debug.ipa: 175 KB
[✓] Assembling Android apk (79.78s)
[✓] Verify HelloSkip-debug.apk: 80,5 MB
[✓] Check Skip Updates: 1.7.2
[✓] Skip 1.7.2 checkup succeeded in 159.89s
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the getting-started guide and the app-development page, especially the omitted virtual-device step and the adb setup described in the report. Clarify the required Android platform tools, PATH configuration, and emulator state before an Xcode build; done means a fresh Mac installation can follow the documented steps without the reported build failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, swift
- Domain
- build-system, documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100