Search Issue Tracker
Fixed
Votes
3
Found in
2019.3.0a1
2019.3.0a9
Issue ID
1168979
Regression
Yes
[HUB] HUB doesn't install the right Android SDK and NDK tools
To repro:
- get the latest HUB
- install the latest version fo 2019.3, with the Android module and SDK and NDK tools
- notice that, in the Preferences window, you'll get a warning that the tools are not installed and the recommendation to install them from the HUB (which we just did)
Reproduces on all 2019.3 (tested on 2019.3.0a9 and 2019.3.0a8)
Does not repro on 2019.2 or 2019.1
On Linux, Both NDK and SDK seem to have issues
On Windows and MAC OS I only noticed the warning for the NDK
Tested on HUB version 2.0.3
-
bri_rivera9
Apr 04, 2020 05:46
I'm using 2019.3.7f1 downloaded it at unity hub there's still warning about missing sdk it's not yet fixed
-
n0alias
Jan 21, 2020 22:30
The problem is during the install, It is hard to notice the dropdown > that lets you check the boxes for the ndk install.. and when you do not check it..it uses the old version 16b instead and doesn't let you upgrade it to anything higher through preferences manually.
-
n0alias
Jan 21, 2020 22:15
The problem is during the install, It is hard to notice the dropdown > that lets your check the boxes for the ndk install.. and when you do not check it..it uses the old version 16b instead and doesn't let you upgrade it to anything higher through preferences manually.
-
xiangyi88889999
Dec 27, 2019 05:26
Still happening with 2019.2.17 and Hub 2.2.1.
-
antifuzz
Dec 17, 2019 14:05
Still happening to me on Hub 2.2.1 and Unity 2019.3.0f3
-
wesp_s
Dec 17, 2019 08:14
Still happening with 2019.2.16 and Hub 2.2.1.
-
visualbruno
Dec 11, 2019 08:39
NDK and SDK are installed, but the path used by Unity is not correct.
(Issue not fixed with Unity 2019.2.15 and Unity Hub 2.2.1)There is a workaround : In Unity
- Go in the Preferences/External Tools
- Uncheck "Android NDK Installed with Unity"
- Select the folder where Android NDK is installed (C:/Program Files/Unity/Hub/Editor/2019.2.15f1/Editor/Data/PlaybackEngines/AndroidPlayer/NDK/android-ndk-r16b) -
j-swan
Nov 30, 2019 09:37
This issue keeps happening to me on 2019.2.14 and 2019.2.12 as well. Extremely frustrating and wasted many hours of my life just trying to build a project that already existed and was running fine.
-
T3hHappyEmo
Nov 29, 2019 15:35
I still have this issue with both 2019.3.0 and 2019.2.14
-
UNITY-DEV01-f3p
Nov 28, 2019 11:23
I'm using UnityHub v 2.2.0 and the issue persists with 2019.3.0f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Fixed with Hub v2.0.4