Closed mcmah309 closed 4 weeks ago
I was able to manually get past this issue with
henry@nixos:~/my_system_config (master)$ echo $JAVA_HOME
henry@nixos:~/my_system_config (master)$ export JAVA_HOME=$(dirname $(dirname $(readlink -f $(which java))))
henry@nixos:~/my_system_config (master)$ echo $JAVA_HOME
/nix/store/5zij17yckck93248rb2grkpm1y3dzy1f-openjdk-21.0.3+9/lib/openjdk
henry@nixos:~/my_system_config (master)$ avdmanager
Usage:
avdmanager [global options] [action] [action options]
Global options:
-s --silent : Silent mode, shows errors only.
-v --verbose : Verbose mode, shows errors, warnings and all messages.
--clear-cache: Clear the SDK Manager repository manifest cache.
-h --help : Help on a specific command.
Valid actions are composed of a verb and an optional direct object:
- list : Lists existing targets or virtual devices.
- list avd : Lists existing Android Virtual Devices.
- list target : Lists existing targets.
- list device : Lists existing devices.
- create avd : Creates a new Android Virtual Device.
- move avd : Moves or renames an Android Virtual Device.
- delete avd : Deletes an Android Virtual Device.
Thank you for reporting this. I'll check it out this week.
please review https://github.com/NixOS/nixpkgs/pull/353914
Describe the bug
avdmanager seem to be using java 11 rather than java 17.
Steps To Reproduce
Steps to reproduce the behavior:
Add
(defined here https://github.com/NixOS/nixpkgs/blob/ca6305bdf65dbc34baf9ad88cbb73f203042a4a9/pkgs/development/mobile/androidenv/default.nix#L18 )
from unstable to your system. Alternatively, since this package is a little heavy, you could use
composeAndroidPackages
instead.Expected behavior
The cli tool should work.
Additional context
From the manual: https://nixos.org/manual/nixpkgs/unstable/#android
Notify maintainers
@numinit @hadilq
Metadata
Add a :+1: reaction to issues you find important.