Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.4.X
Votes
0
Found in
2017.4
2017.4.28f1
Issue ID
1170776
Regression
No
[Android][2017.4] Editor doesn't update NDK's directory until the project is re-opened
Repro steps:
1. Create a new project and switch build target to Android and Scripting Backend to IL2CPP
2. In Preferences -> External Tools -> NDK write anything or choose whichever directory
3. Start a build
If there was already a valid NDK selected before opening the project the build will succeed because the Editor doesn't update the NDK variable
4. Close and re-open the project
5. Try to build
Actual: Build fails because NDK's location is re-read only when the Editor is reopened
Reproducible with: 2017.4.30f1
Not reproducible with: 2018.1.0a1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a10
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Horst6667
Sep 10, 2019 14:31
The issue is still present in 2018.4.8f1 and currently makes it impossible for me to use BuildPipeline.BuildPlayer at all.
The NDK path is lost randomly every few builds.
The issue could be connected to the changes in UnityEditor.Android.Extensions.dll which were introduced in 2017.4.16f1 as this user pointed out:
https://forum.unity.com/threads/cant-locate-android-ndk-in-batch-mode-after-2017-4-16f1.595786/