-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmdline-tools : could not determine SDK root #167
Comments
👀 |
Hi @wtto00 ! Under what conditions does this Issue occur? |
Hello, thank you for your reply. I would like to start an emulator in CI. Please wait a moment while I write an example to reproduce it. |
When installing an SDK, I must add the parameter jobs:
# This workflow contains a single job called "build"
build:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
- name: Setup JDK 17
uses: actions/setup-java@v3
with:
java-version: 17
distribution: temurin
- name: Setup Android SDK
uses: amyu/setup-android@v3
# Runs a set of commands using the runners shell
- name: Run a multi-line script
run: |
sdkmanager --install "system-images;android-31;default;x86_64"
avdmanager -s create avd --name Android_Emulator --package "system-images;android-31;default;x86_64"
$ANDROID_HOME/emulator/emulator -list-avds
$ANDROID_HOME/emulator/emulator -verbose -avd Android_Emulator When I added the But how do I use the installed SDK? When I use The demo: https://github.com/wtto00/demo-setup-android/actions/runs/6212159784 |
Thanks for the demo! I understand the problem. I have also found another problem and will fix it in V3 |
Wonderful! It works. https://github.com/wtto00/demo-setup-android/actions/runs/6213341498/job/16864301420 Thanks for your great work! |
@wtto00 |
See this: https://9to5answer.com/cmdline-tools-could-not-determine-sdk-root
Please place
cmdline-tools
under theANDROID_HOME
directory, with the following directory structure:$ANDROID_HOME/cmdline-tools/latest/bin/avdmanager
.The text was updated successfully, but these errors were encountered: