IssueTracker

can you share your android studio version

Is this happening with Studio 3.0?

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

@omar.kilani Just a note, the warning about ndk is just a warning.  It does not cause the build to fail.  It looks like for whatever reason, the build is unable to find buildtools 25.0.3.  In any case, the build failure is not related to this bug.

Same problem for me. Not using NDK.
No env var ANDROID_NDK_HOME set, no ndk.dir in local.properties.

The default printout is:
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to F:\dev\adt-bundle-windows-x86_64\sdk\ndk-bundle.

If I set it to an empty value in local.properties:
ndk.dir=

The printout is
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to F:\dev\gc\runnerup.

So local.properties can override

This probably started with latest build-tools, AS 2.3-beta1

ag/I7d8a39a10bbaa35d670594079bd24587c4be9d91

same problem here. no NDK packages downloaded, nothing is set either in ANDROID_NDK_HOME or local.properties - and yet I get warnings :

NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /home/myusername/Android/Sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.

Same here but not quite. But also new with tools 2.3.

I have NDK_ROOT=/home/kman/Android/android-ndk-r10e set in the shell.

This is a valid NDK directory which I've used to build some native code (the artifacts are checked into source control, so don't get rebuilt every time).

There is no "platforms" directory inside that, but it worked fine.

The warning given by Gradle mentions an entirely different directory:


NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /home/kman/Android/android-sdk-linux/ndk-bundle.


I, same as the people above, do not set ndk.dir in the project's "local.properties".

The "/home/kman/Android/android-sdk-linux" is my Android SDK location obviously. It is set in Android Studio's "Project Structure".

There is *no* "NDK location" in Android Studio's "Project Structure", again same as reported above.

So it looks to me that tools 2.3 will "assume" the NDK location based on the SDK location:

NDK = SDK + "/" + "ndk-bundle" = "/home/kman/Android/android-sdk-linux/ndk-bundle"

This directory, for me, does not exist. There are no native build steps in the project.

And so, the issue looks to me like this:

1 - Tools 2.3 try to "configure" NDK related stuff -- even if the project does not use the NDK. Prior to 2.3, this did not happen (or was done "lazily", "on demand").

2 - The structure of NDK directories has changed, my NDK folder which worked before does not have a "platforms" subdirectory, but the new structure does (looks like).

Point 1 is the real regression here.

2.3 is officially out and I'm still seeing this problem.

I'm using react-native 0.42 and I have no concept of NDK, nor do I believe I'm using it. I don't understand how to make this warning go away. There is no mention of ndk in my local.properties and nothing is set for it in my "project structure" in android studio.

When it says "If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning." in the warning, I really want to know how to unset the variable for ANDROID_NDK_HOME. I have no idea where that variable would exist.

I am also facing this issue, did not define any NDK directory as we are not using it.

I also am suddenly experiencing this issue, just updated Android Studio the other day and now I'm getting the same exact error everyone else is reporting.

The only thing my project local properties has is:
sdk.dir=D\:\\Coding\\Android\\sdk

and my project has absolutely no relation to NDK or its use thereof.

However, once I fixed the SDK target and updated from 23.0.2 to 25.0.0 in the project's different target's build.gradle, the error went away and I was able to export my AAR with no errors or warnings.

Mike, I started seeing this when I upgraded AS yesterday as well.  What do you mean by "fixed the SDK target"?

the same problem here. I upgrade the android studio to 2.3 and gradle and build tools.

android studio and my ci server both report the problem

getting this error on a gradle-built project that uses neither AS nor the NDK.

I can confirm that neither is ANDROID_NDK_HOME set nor does local.properties have an ndk.dir var set.

I'm also seeing this after upgrading.

Further to this, you will get one of these NDK warnings for each Android based  submodule in your project as well. i.e., just run "clean" in a project with one submodule, and you will see the NDK warning twice.

If you install the NDK the warning goes away.

Just upgraded to 2.3 android studio and am also seeing this issue on OSX.

No NDK usage / NDK variables set anywhere

[Comment deleted]

Long story short, this warning happens after I updated an old project. I'm surprised that the more I dig, the more I realize I'm not getting any more specific messages. Basically I can get more info, but the most specific thing I get it "There is an error inside a gradle task", and maybe the config task.
From what I can tell, Android Studio used to use Jack, now it doesn't. It used to use external Java dir and now it doesn't. So if you take a perfectly working project and upgrade it, you will get that error and many more, and none of them will tell you where the issue is. In hopes that it helps somebody, I downloaded Gradle externally, and Java, then ran a trace. My primary problem, currently, is javaCompile action. I have about 30 dependencies to check b/c I took over someone else's code and they like dependencies a lot more than I do, but I do maintenance and they do initial... I'm thinking maintenance makes you dislike dependencies.

The good news is, the errors are already nonspecific so I don't have to cut anything, here's the raw message.

Edit n(bug report): If you attach a file then mistype the captcha, it doesn't retain the attached thing... re-uploading this comment.

Still seeing this. Was it supposed to be fixed in this version?

classpath 'com.android.tools.build:gradle:2.3.1'

My company is seeing this on both of our android apps as well.

We lost the target tag since the migration of issue tracker.  The fix is targeted for 2.4.

@feitingschatten1 If you are still seeing the issue, you probably want to file a new bug with more information.  The compile error is not related to this warning.

It is NOT fixed! I am on latest Gradle and still experience this behavior.

It was fixed in the android gradle plugin (not gradle itself) and as stated above the fix was targeted for 2.4 (2.4.0 isn't released yet, currently only alpha versions are available.)
"I am on latest Gradle" (currently 3.5) wouldn't fix the issue, updating the android gradle plugin however does.

After replacing the line
classpath 'com.android.tools.build:gradle:2.3.1'
with
classpath 'com.android.tools.build:gradle:2.4.0-alpha7'
in build.gradle i no longer see the NDK warning message. So I can CONFIRM it as FIXED.
(i am using gradle 3.5 and the android plugin 2.4.0-alpha7)

same problem here !!

Same problem here!

I'm still seeing this issue on com.android.tools.build:gradle:3.0.0-alpha3

For people experiencing this with plugin 3.0.0+, please file another bug with more details including the following:
- Are you using NDK in your project?
- Do you have a local.properties file?  If so, is ndk.dir set to a directory?
- Is the environment variable ANDROID_NDK_HOME set?
- Have you downloaded the NDK bundle from the SDK manager?
- The warning message shows what the plugin thinks the NDK directory is set to.  Does it point to a valid NDK directory?

Please also include the actual warning message.  Thanks.

it's so hard to not write a bitchy comment about Google's lack of interest in fixing bugs

I'm getting this error as well. local.properties does not contain ndk.dir.

NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /Users/elllee/.android-sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.

For anyone still experience this issue on plugin 3.0.0-alpha1 or later.  Please file a new bug and try to answer *all* question in #33.  We need more information to debug the problem and adding comments to a closed bug is an easy way for it to get lost.

To give a bit of background, the plugin checks whether the NDK directory is valid.  Most likely, you are not using NDK.  We automatically assume it's in {sdk}/ndk-bundle.  It will be ignored if {sdk}/ndk-bundle does not exist.  If you see 'NDK is missing a "platforms" directory.', it means there is an {sdk}/ndk-bundle, but not a {sdk}/ndk-bundle/platforms directory.  This means you have a corrupted NDK for some reason.  It is safe to just remove {sdk}/ndk-bundle if you are not using it.

#36 is correct: Deleting the empty folder helped.
RANT: Way to go Google, rather have developers fix it themselves locally instead of fixing it once in your product *clap* *clap* *clap*

Hi Peter, if you know how the empty ndk-bundle folder got created, we would appreciate it if you can file a bug to tell us.  Then we would be able to track down and fix the problem.
The check is there to prevent the build from silently ignoring critical issues that would result in worse runtime problem.

I'm getting this problem in a Unity 2017.4.2f2 project.

Same problem when building react native project using the command ' ./gradlew assembleDebug '

I've created a new issue, as it still occurs:
https://issuetracker.google.com/issues/119968482

what is the bug i am not able to install and develop android app

If you meet this error, refer below.

Solution:
1. used ndk:
use ndk 16r
  or
copy the missing toolchain folder (such as mipsel-linux-android) from ndk 16r to your ndk
   or
 use cmake ( i have no try by this way)



2. not use ndk

Note:
 use android gradle plugin 3.1.0+