NDK version is UNKNOWN [duplicate] - java

After updating Android Studio and Gradle to 3.5,
I now get this error:
NDK Resolution Outcome: Project settings: Gradle model version=5.4.1, NDK version is UNKNOWN
I changed the Gradle version in build-gradle back to 3.4.2 but it didn't help.

I had similar problem and solved it by opening project using Import project (Gradle, Eclipse, etc.) instead of Open existing Android Studio project.

You can download NDK from File>Project Structur>Choosing SDK location from left panel and pressing Download from NDK location part.

I was having the same issue after upgrading my android studio. You just need to open local.properties & change ndk.dir path to your NDK path.
Code:
ndk.dir=D\:\\Android\\SDK\\ndk-bundle
sdk.dir=D\:\\Android\\SDK

I don't use NDK in my project, but I had the same problem. The problem disappeared after I updated the SDK version to the newest
compileSdkVersion 29

I had a previous answer (since deleted by moderators) where I detailed that there are workarounds (as listed here) that work for some but that there is an underlying bug in gradle because the workarounds don't work for everyone (specifically: none of them work for me)
The related google issue is here: https://issuetracker.google.com/issues/140403764
Update: As of today (20190920) they indicate that they have fixed the underlying issue, so I would expect a future release of gradle after today (20190920) will contain the fix.
Update2: Today (20190926) I received a response from a googler that the problematic code was in Android Studio and it is contained on the 3.6-release branch but is not available on any publicly available build at the moment (Android Studio 3.6 Canary 12 was released just before this fix was made). That lets you know which component to update and which versions to pay attention to, anyway. Looks like Android Studio 3.6 Canary 13 and later should have it https://issuetracker.google.com/issues/140403764#comment13
Until then you can try the workarounds but when there's a vendor bug and workarounds don't work you just have to wait for a vendor patch.

You need to install NDK using the SDK manager

I first got this issue after upgrading from Android Studio 3.5.0 to 3.5.1 today.
I simply did a rebuild from the top menu Build --> Rebuild Project.
This might not work for everyone depending on what caused the issue but it worked for mine. Give it a shot.
(Also, I do not use the NDK and never have downloaded it before. Still don't have it downloaded)

If you are not using NDK, ignore the error.
I have installed NDK to see if this makes any difference. There is no difference (except for an unused NDK folder of more than 2 GB :). So I removed it (i.e. delete the ndk folder and remove NDK environnent variable you have set previously).

After my recent Android Studio upgrade I had the same error message. I tried the other answers here and none worked. But #Zahra's answer pointed me to something that did work:
Go to File->Project Structure...
Under "Android NDK Location", click the dropdown and select the "DEFAULT NDK Recommended" option.
There was a slightly different path in there before I selected the default. Somewhere upgrading using the SDK manager, the path seems to have changed.
And now in the local.properties file sdk.dir is set to the same directory as the "DEFAULT NDK Recommended" option.

i fix it by going to file > Invalidate Caches\Restart
the IDE will restart and the problem will fix

I had same problem. My environment is:
Android Studio 3.5.1
Gradle 4.4
Android-Gradle-Plugin 3.1.2
CMake 3.10 and 3.6
I uninstalled CMake 3.10 by SDKManager. (installed CMake is 3.6 only)
Gradle sync and build succeeded.
(1)
android-gradle-plugin 3.1.2 used CMake 3.10.
In android-gradle-plugin 3.1.2 (or 3.1.+), feature of support for CMake 3.7 and higher is a preview feature.
(from output message of gradle assembleDebug or gradle sync.)
(2)
https://developer.android.com/studio/projects/add-native-code.html#use_a_custom_cmake_version
The SDK Manager includes the 3.6.0 forked version of CMake and version 3.10.2. Projects that don't set a specific CMake version in build.gradle are built with CMake 3.6.0.
Perhaps this behavior is android-gradle-plugin 3.3 or higher.
(it is from android-studio 3.3 that can be downloaded CMake 3.10)
android-gradle-plugin 3.1.2 used latest version from installed CMake.

I had the same issue on a mac as well.
Suggestion: Force the .gradle folder to rebuild itself..
This still shows the 'NDK Version is UNKNOWN' in the Event Log yet it builds successfully and doesn't give me any issues. (I don't have NDK downloaded)
Open your /Users/macuser/ folder
Press CMD + SHIFT + . (dot/period) to view hidden folders
DELETE .gradle folder
Restart Android Studio
This will cause Android Studio to rebuild and re-download your .gradle folder fixing your conflicting files in the process.

The problem is solved when I updated the Android Gradle Plugin Version from 3.1.4 to 3.4.0 and the Gradle Version from 4.4 to 5.1.1 at the same time. Of course, I downloaded the newest NDK(Side by Side) with SDK manager.

In my case, Android Studio was installed on a new mac. Just needed to download Android 9 (my target/compile SDK was 28) and build tools. The problem was solved after this.

In my case i fix it by upgrade to SdkVersion 29 and migrate to AndroidX.

After upgrading I've got the very same problem in one of my projects.
I solved it just deleting the line ndk.dir=D:\Android\SDK\ndk-bundle from the local.properties file.

I had the same error after adding a couple of libraries in the app-level build.gradle file.
The solution was just to clean the project.
In the menu bar choose: Build >> Clean Project
After that, the error was gone for me. I didn't do anything else.

I got this error (and several others) after importing a project from version control via Bitbucket hyperlink.
Once imported, close the project and re-import it using File > New > Import Project. After that everything built correctly.
(The NDK path was already specified properly, and only importing as new worked)
Meta:
Android Studio 3.5
Build #AI-191.8026.42.35.5791312, built on August 8, 2019
JRE: 1.8.0_202-release-1483-b49-5587405 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
Gradle 3.4.0

Problem solved for me after checking Suggestions in Project structure and updated the two suggested updates. Sorry I can't remember the module names as they disappeared as soon as I pressed update for each of them and graddle sync. started automatically and after this problem disappeared

downgrading ndk version from 20 to r17c and cmake version from 3.10 to 3.6.411459 solved the problem for me

I had the same problem after updating Android Studio.
My problem is solved by after updating Android SDK Build-Tools.
[Tools->SDK Manager->SDK Tools->Android SDK Build-Tools].
Then try to Clean the project
[Build->Clean Project].
Finally restart the Android Studio IDE......

I just closed project, closed android studio, restarted my PC, tracked my project and deleted the .Idea folder in "B:/PROJECTNAME/.idea" and voila.
Problem solved. It resyncs. N/B: my gradle is androidx. goodluck to someone.

Change the claaspath to 'com.android.tools.build:gradle:3.5.2' in build.gradle script

Ok. I recently downloaded the latest version of Android studio and got similar error. So eventually I created a new project.
Selected Kotlin Language then Jelly Bean (talking 'bout the options to pick from).
Then the whole synching began but the 1st sync failed and eventually it auto-synced again and everything began to work.
Did modify the default codes (text) since I'm a beginner but got no error messages.
The preview was OK and I continued my learning.
Sorry I couldn't explain it better. I'm just a beginner.
Oh! You need to be connected to the Internet for it to work.

If this problem occurred after an Android Studio upgrade and you initiated a plugin update from right bottom notification: Open File > Project structure, then change the Android Gradle version to your Android Studio version and downgrade the Gradle version to the previous one.
In my case, I downgraded the Android Gradle plugin from 3.5.3 to 3.2.1 and the Gradle version from 5.4.1 to 4.6.

I modified the gradle version of the gradle-wrapper.properties file from 4.1 to 4.6.

I had this problem and none of the solutions worked for me. Problem is, this error or warning might appear for very broad reasons. You can follow these steps to find out what is wrong:
NDK is missing
When Gradle starts to compile native dependencies it creates ".cxx" folder in your "app" folder. inside that folder you can find "ndk_locator_record.json" file, which is very strange type of log file. It is basically all the paths Gradle checks to find NDK folder. If there is any error or mismatch on NDK version numbers you can see in this file.
NDK build fails
for some unknown reasons (maybe bug in Gradle) ndk build does not show actual error on event log window, instead it shows a failure, like Gradle sync failed: executing external native build for ndkBuild .... following by NDK Resolution Outcome: Project settings: Gradle model version=5.4.1, NDK version is UNKNOWN.
In this case go back to .cxx > ndkBuild > debug > x86(x64 or any other cpu arch)
Here in this folder you can find "json_generation_record.json" file, it is same type of log, usually last entry has the actual error. For example, for me was
../../sdk/native/jni/OpenCV.mk: No such file or directory
make: *** No rule to make target '../../sdk/native/jni/OpenCV.mk'. Stop.
From here you have a starting point to find out what is going wrong under hood.

If the NDK is not install, and the Android Project requires it then first install the NDK.
On windows OS add the NDK path to PATH environment variable. This will fix the version issue.
In my case the NDK path is
C:\Users\\AppData\Local\Android\Sdk\ndk\21.0.6113669

I faced this issue before and I fixed it by making sure to have the right permissions to the app directory.
I am using macOS, so I did:
chmod -R 777 your_android_project
and the issue was gone.

i have this problem too when I updated the Android Gradle Plugin Version from 3.1.2 to 3.5.1
Here is how to solve this issue :
Go to gradle.properties file in root folder of your project and add android.useDeprecatedNdk=true

Related

Gradle build is stuck and never finishes after updating to Android Studio 3.2

I have a project in android and after updating to android studio 3.2 Gradle build is stuck and never finishes. I looked at the task manager and the Open JDK Platform Binary task is going to suspended a few seconds after i start the build. Anyone has seen something similar?
I have distributionUrl=https://services.gradle.org/distributions/gradle-4.6-all.zip
Deleted the .gradle folder and tried again
My build tools version is buildToolsVersion '26.0.2' and version of gradle is 'com.android.tools.build:gradle:3.2.0
Changed compile to implementation
I have no idea why the task is suspended but that is why the build gets stuck when i try from the terminal a Java Platform Binary task is generated and this is not suspended.
Any help would be appreciated.
I managed to solve it by changing the SDK location (File->Project Structure->SDK location) and point to a different path on the JDK location, i had another version of JDK so using that it doesn't suspend the task of Open JDK Platform Binary. At least this change allows me to sync and build the project.
I had the same issue and I solved it by downgrading Android Studio to 3.1.4 version. You can download it from here: https://developer.android.com/studio/archive
You can keep both versions, and you can use the same Android SDK Folder. However, I reccommend you to select "Do not import settings" option on the installation process. Regards.
Deleting both the "/build/ and "/app/build/" folders solved my problem!

Android Studio Gradle Sync Failed - Unsupported Java

I'm on Linux (Arch Linux) and using Android Studio 2.3.1
When creating a new empty project in Android Studio I get the error:
Gradle sync failed:
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(Ljava/lang/String;Lorg/gradle/api/JavaVersion;)V
Consult IDE log for more details (Help | Show Log)
It seems that there is something with the java version. I have openjdk-8 installed and also tried with Oracle JDK version 8 (also tried with version 7).
Things i've tried:
Using installed gradle or gradle that comes with Android Studio
Removing ~/.gradle and ~/.android.
Update:
If I enter the project directory and run gradle build i.e. using my installed gradle version it seem to build. However, being able to run gradle from Android Studio seem essential to even use Android Studio.
I upgraded to Android Studio 2.3.2 and then this particular problem was solved.
I did not use the package from AUR (Arch User Repository) when upgrading, instead I used the Android Studio "Check for updates" and upgraded that way. I don't know if that matters.
Update:
Happened again when upgrading to Android Studio 3.0.1 from AUR. Installing the official build from http://developer.android.com works though so it's some issue with the build in AUR for ArchLinux.
I had the same problem AFAIK.
Firstly I had a version previous to 3.0.1 of Android, then I downloaded the Android zip package from the official website, then installed it and kept the same old preference files (or so). Then this problem appeared. What I did is uninstalling (thus deleted the android-studio folder in terms of Ubuntu) and installing it back again and it was solved.

Eclipse gluon new project does not finish

I use Eclipse 4.7 (Oxygen), portable version
Android Development Tools (no version ?), with SDK Manager => SDK Tools 25.5, Android 6 and 7 (API 23, 25), Android Support Repository, SDK Platform, SDK Platform-tools
Gluon plugin 2.4.0
E(fx)clipse 2.4.0
Gradle IdePack 3.8.x +1.0.x
SceneBuilder installed and configured in Eclipse
and (MarketPlace, Enide 2015)
new Gluon project begins well:
name and location (default)
Gluon Application Settings (default)
Name of view (default)
=> button finish appears active, but when pressing it, nothing happens. This window blocks here and no message. Only back button, close and cancel work.
I'v tried any combination of projects (Desktop, Mobile, single view, multiple, Fxml), and checkbox, but it doesnt change anything.
Have anyone encounter the same problem ?
Or is there any log to search for anywhere ?
thanks
The plugin has been updated (version 2.5) to work with Eclipse Oxygen and Gradle 2+. Install the new plugin (it will uninstall the old one) and it'll work again. See here for details.
i had the same error with Neon and it all boiled down to an exception i saw in the .log File of eclipse ({yourWorkspace}.metadata).
java.lang.ClassNotFoundException: org.eclipse.buildship.core.workspace.SynchronizeGradleProjectJob cannot be found by com.gluonhq.eclipse.plugin_2.4.0
It seems version 2.x of Buildships Gradle has rearranged its packages and contents making the finish button unclickable.
I downloaded the latest 1.x version from an updatesite which can be found on github and everything runs just fine.
Hope this helps,
Bests!
Firstly, sorry for my english.
I was having the same problem as the guillaume girod-vitouchkina. I could not create a new Gluon project. I was using Eclipse Neon.2 and update for Eclipse Neon.3 and the problem persisted. So I did what uBreckner recommended and it worked! I uinstall version 2.x of Buildships Gradle and install latest 1.x version.
Thanks guys,
Regards!

Android Studio - Gradle sync error

I have a synchronization error in Android Studio.
I Use: 1.0.2 version from canary channel.
Gradle: I tried with version 2.2.1(downloaded from https://www.gradle.org/downloads) and self-download version.
JDK: jdk1.8.0_05
I created a new project and the error is always the same:
Error:Unable to find method
'org.objectweb.asm.ClassReader.getMaxStringLength()I'. Possible causes
for this unexpected error include:Gradle's dependency cache
may be corrupt (this sometimes occurs after a network connection
timeout.)
I tried resolve the issue with the invalidation of cache method, and stopping Gradle daemon, but nothing..
Delete the .gradle directories both in your home directory and at the top level of your project. Gradle's cache directoires aren't affected by the "Clear caches and restart" option.
After updating to Android Studio 2.3 I received this error and the top answer didn't work. Following an answer from here I finally got it fixed.
Go to
gradle → wrapper → gradle.wrapper.properties
And change to distributionUrl to the following:
distributionUrl=https\://services.gradle.org/distributions/gradle-3.4.1-all.zip
Sorry for a late answer but I hope it will still be useful. I faced the same problem and deleting .gradle directories didn't help.
Try to reinstall your JDK. In my case I uninstalled my JDK 1.7.0_60 (x64) and JDK 1.8.0_5 (x86). Then I installed JDK 1.8.0_45 (x64) and the problem has gone. HTH.

Android Studio Gradle project sync failed

I'm getting error:
"Gradle project sync failed. Basic functionality (e.g. eiditing) will not work properly."
And Error Log:
Error:Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.10/userguide/gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM Could not reserve enough space for object heap Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I was trying to delete .gradle folder as I read here. This worked yesterday but today when I started Android Studio the error showed again and deleting .gradle folder doesn't help.
I realy don't know what to do.
Does anyone have any suggestions?
Just a blind guess: try to add something like this to your gradle.properties file in the project:
org.gradle.jvmargs=-Xmx512m -XX:MaxPermSize=512m
Same issue solve in Android studio by
File -> Settings -> Compiler (Gradle-based Android Projects)
Change the "**VM options**" to
-Xmx512m -XX:MaxPermSize=512m
It worked for me .
The only way I've been able to fix this when it happens is by doing
./gradlew clean
and
./gradlew --refresh-dependencies
and then restarting Android Studio.
If that doesn't work I usually resort to reimporting the project.
I had the Same Issue, and Searched for almost 4 Days but can't able to solve the problem.
But at Last I can able to solve the problem, and for that please follow the steps.
Step 1: Check Your Java Version.
Step 2: If It is 1.7 then Download the New Version i.e JDK 1.8
Step 3: Install JDK 1.8
Step 4: Change the Java Version of Android Studio to 1.8 and the
problem solved...
It Worked for me.
changing compile setting to this worked for me
I was getting the same error in version 2.2.3,So I downloaded the latest Android Studio version 2.3.3, even in the latest version, I was getting the same error, below is my solution :-
Download the latest version of Android Studio from the official site.
In File>Project Structure>SDK Location, JDK Location should refer a 64-bit JDK ex. C:\Program Files\Java\jdk1.8.0_131, even after this, error was not fixed completely.
I checked the project structure, In the File>Project Structure>Project , the Android Plugin version was still 2.2.3, I changed it to 2.3.3 and the build is successful and everything is working smoothly.
This one worked for me.
Close the Android Studio
Delete .gradle folder from c:\users\{username}\.gradle
Open the Android Studio
Clean Project
Rebuild Project
Sync Project with gradle files. See screen shot
Cheers!
Check if the gradle path in File -> Settings -> Build, Execution -> Gradle is correct. I had incorrect path to local gradle distribution there.
None of these worked for me, so this is how I eventually solved my problem:
In the top-level build build.gradle file, remove
'classpath 'com.android.tools.build:gradle:some version number'
sync your project and make sure your gradle location is pointing at the correct directory
Updating Java and the problem is solved!
Control panel > Java > Update Now
I was in that situation, finding near no solution; finally I realized that my firewall was blocking java executable from opening ports/connecting. Try adding a firewall exception for the Java executable. This solved the problem for me.

Categories

Resources