NativeScript / NativeScript/nativescript-cli

WARNING: The Android SDK is not installed or is not configured properly.

Offen
#4,265 3 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

bug severity: medium
Vorherrschende Sprache
JavaScript
Sterne
1.1k
Forks
204
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
8

Beschreibung

I followed all instructions in this official page NativeScript Advanced Setup: Linux.

I only got stuck at this step:

sudo apt-get install lib32z1 lib32ncurses5 libbz2-1.0:i386 libstdc++6:i386

for which I had to first run:

sudo dpkg --add-architecture i386

Regarding emulators, I chose genymotion. (did not install avd)

Now, after installing everything, here are all relevant environment settings/info I could get:

$ lsb_release -a
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic

$ node -v
v8.10.0

$ javac -version
javac 1.8.0_191

# installed latest android packages for Android 28
$ sudo $ANDROID_HOME/tools/bin/sdkmanager "tools" "emulator" "platform-tools" "platforms;android-28" "build-tools;28.0.3" "extras;android;m2repository" "extras;google;m2repository"

$ ls /opt/android-sdk
build-tools  emulator  extras  licenses  patcher  platform-tools  platforms  tools

$ echo $PATH
/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

$ adb version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as /opt/android-sdk/platform-tools/adb

$ tns --version
5.1.0

$ node
> process.env.ANDROID_HOME
`/opt/android-sdk`
> process.env.JAVA_HOME
'/usr/lib/jvm/java-8-oracle'

$ echo $ANDROID_HOME
/opt/android-sdk

$ echo $JAVA_HOME
/usr/lib/jvm/java-8-oracle

Now I finally check tns doctor...

There seem to be issues with your configuration.
✔ Getting NativeScript components versions information...
✔ Component nativescript has 5.1.0 version and is up to date.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Local builds for iOS can be executed only on a macOS system. To build for iOS on a different operating system, you can use the NativeScript cloud infrastructure.
✖ WARNING: The Android SDK is not installed or is not configured properly. 
 You will not be able to run your apps in the native emulator. To be able to run apps
in the native Android emulator, verify that you have installed the latest Android SDK 
and its dependencies as described in http://developer.android.com/sdk/index.html#Requirements 

As you can see, tns doctor says everything is fine... but not really.
Precisely, I don't get the

"✔ A compatible Android SDK for compilation is found."

Vs

"✖ WARNING: The Android SDK is not installed or is not configured properly."

Is that even possible ?
Any idea of any further investigations I should do ?

P.S: please, this is not the same problem as #3585 where adb is clearly in cause... #3585 title should be : "WARNING: adb from the Android SDK is not installed or is not configured properly." which is quite different

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit dem Einstiegspunkt tns doctor und reproduziere den Bericht mit den im Issue aufgeführten Versionen von Ubuntu, Node.js, Java, NativeScript und dem Android SDK. Vergleiche die erfolgreichen Prüfungen mit der separaten Warnung zum nativen Emulator und prüfe die im Bericht verlinkten Anforderungen an die Einrichtung des Android SDK. Als erledigt gilt die Aufgabe, wenn das Verhalten der Warnung erklärt ist und die Diagnose die Konfiguration korrekt widerspiegelt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
android, java, javascript, node.js
Bereich
cli, devtools, mobile
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.