skiptools / skiptools/skipstone
`skip doctor`/`skip checkup` doesn't attempt to connect to the Android emulator
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 106
- Forks
- 20
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 9
Description
If you skip create or skip init an app project, by default, it's going to be configured to attempt to launch your app whenever you build.
skip checkup attempts to build and export an IPA and an APK, but it won't attempt to test installing/accessing a running emulator. It won't even run adb to see if it can detect a device.
We've recently had reports on Slack of users having issues during Skip build, not finding running emulators. Ideally, skip doctor would run adb devices to ensure that we can detect a running device, and skip checkup would install the app on a running device, allowing us to reproduce any issues with a single command.
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
Start at the skip doctor and skip checkup command entry points, then trace how each currently builds, exports, and launches apps. Use adb devices as the detection check for doctor; checkup is done when it also attempts installation and access on a running emulator, with failures surfaced through the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, swift
- Domain
- cli, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100