Skip to content
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

/bin/sh: sdkmanager: command not found #123

Closed
SDGGiesbrecht opened this issue Jan 13, 2021 · 9 comments · Fixed by #124
Closed

/bin/sh: sdkmanager: command not found #123

SDGGiesbrecht opened this issue Jan 13, 2021 · 9 comments · Fixed by #124

Comments

@SDGGiesbrecht
Copy link

For the last day or two, all actions have been failing with this message:

Installing latest build tools, platform tools, and platform.
/bin/sh -c \sdkmanager --install 'build-tools;30.0.3' platform-tools 'platforms;android-29' > /dev/null
/bin/sh: sdkmanager: command not found
/Users/runner/Library/Android/sdk/platform-tools/adb -s emulator-5554 emu kill
error: could not connect to TCP port 5554: Connection refused

As recently as four days ago, actions were successful, and logs appeared as follows. Note the additional first step.

Installing new cmdline-tools.
/usr/bin/unzip -q /Users/runner/work/_temp/1f68391f-809c-4848-9a14-8eca0e8ed308
Installing latest build tools, platform tools, and platform.
/bin/sh -c \sdkmanager --install 'build-tools;30.0.3' platform-tools 'platforms;android-29' > /dev/null
Installing latest emulator.
/bin/sh -c \sdkmanager --install emulator > /dev/null
[...]

I can see from your repository’s main page that the latest release was 8 days ago. That suggests to me that the change was not in your code, but with the underlying GitHub’s host. Maybe they added a partial installation of the command line tools, which tricks your action into believing it already has everything it needs even though it actually doesn’t?

@ychescale9
Copy link
Member

Can you try to ping the android-emulator-runner version to v2.13.0?

Can you share your workflow and a full log?

@SDGGiesbrecht
Copy link
Author

Can you try to ping the android-emulator-runner version to v2.13.0?

I’ll try and get back to you.

Can you share your workflow and a full log?

I doubt they will help, but here is one such workflow and corresponding log.

@SDGGiesbrecht
Copy link
Author

Can you try to ping the android-emulator-runner version to v2.13.0?

Here are the commit and log.

@ychescale9
Copy link
Member

Ah I see. You're using macos-11 which has the cmdline-tools installed so this action skips the initial downloading and configuration of the cmdline-tools, which also skips adding the path for sdkmanager etc.

I'm fixing it now.

@ychescale9
Copy link
Member

macos-11.0 should be supported now. Let me know if it works for you :)

@SDGGiesbrecht
Copy link
Author

Yes, it works now. Thanks.

@s-ayush2903
Copy link
Contributor

@ychescale9 We're still getting the same problem even on updating the runner version to 2.13.0, can you help us with that.
Run: https://github.com/kiwix/kiwix-android/pull/2562/checks?check_run_id=1783849832
Commit(that updates rc version): kiwix/kiwix-android@574cca8

Also to mention that our nightly build is also failing since last two days, the reason being the same, yeah I admit that we haven't runner version in nightly we've done so in our coverage reporting but still they're failing, can you please look into it

@ychescale9
Copy link
Member

ychescale9 commented Jan 28, 2021

The fix is available in the latest release 2.14.3. You can also use the latest version instead of pinging to a specific version to get the latest update: ReactiveCircus/android-emulator-runner@v2.

@s-ayush2903
Copy link
Contributor

Thanks for help, it fixed all failures! 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants