Search Issue Tracker




Found in



Issue ID




[Android] Invalid Android NDK Directory get detected when 'Android SDK and NDK Tools' installed through HUB



When 'Android Build Support' Module installed with 'Android SDK and NDK Tools' through HUB then in Editor Preferences Invalid Android NDK Directory(NDK 19.0.5232133) get detected.

Invalid Android NDK Directory -> NDK 19.0.5232133
Recommended Android NDK Directory -> NDK r21d (64-bit) 21.3.6528147

How to reproduce:
1. Open Unity Hub(2.4.1 ) > Installs > 2021.1.0a1
2. Add Modules > Android Build Support > check 'Android SDK and NDK Tools'.
3. Create new project > Switch platform to Android
4. Go to Preferences > External Tools > Android NDK version installed
5. Disable 'Use embedded NDK' and Select a folder where your NDK installed and provide that path

Actual Result:
Invalid Android NDK Directory get installed when 'Android SDK and NDK Tools' installed through HUB

Expected Result:
By Default, Recommended Android NDK Directory should install when 'Android SDK and NDK Tools' installed through HUB

Download and Give the path of Recommended Android NDK Directory externally

Reproducible in:

Working Fine on:
2020.2.0b7, 2020.1.8f1

Occurring on Windows 10 , Mac 10.15 and Ubuntu 18.04

-Without workaround unable to build an android player, Build failed with
UnityException: Android NDK not found
-On using workaround able to make android build with 'Mono' Scripting Backend but it failed for 'IL2CPP' Scripting Backend

  1. Resolution Note:

    Fixed on Hub v2.4.2

Comments (5)

  1. hippogames

    Nov 18, 2021 11:10

    Regression in 2020.3.22 / Hub 3.0.0
    I've created a new bug

  2. ahmedaniss

    Jun 05, 2021 07:48

  3. ahmedaniss

    May 30, 2021 13:24

  4. ahmedaniss

    May 17, 2021 16:14

  5. Vynh

    Nov 24, 2020 16:29

    I'm running into this issue with 2020.1.0a7

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.