Missing packages do not seem to be installed.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by tracing the emulator configuration flow and the step that invokes android list sdk -u. Reproduce the missing-package cases described in the issue, then verify that all required Android packages are installed before emulator configuration begins.
Written by the indexing model from the issue text.
Description
Seen two cases where missing Android packages were not being installed prior to configuring the emulators. Its possible the missing required packages are not showing up when calling android list sdk -u.
- Dominant language
- Ruby
- Stars
- 17
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Automattic/android-emulator-builder
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in Automattic/android-emulator-builder
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
hitobito/hitobito_pfadi_de#164 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Text
Difficulty 2/5 1-3 hours Newbie friendliness 65/100