Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.4.X
Votes
0
Found in
2017.4.16f1
2017.4.28f1
Issue ID
1188823
Regression
No
[Android][2017.4] Editor doesn't update NDK's directory when using EditorPrefs.SetString until the project is re-opened
Repro steps:
1. Open attached project and clear the NDK location in Preferences -> External Tools
2. Close and re-open the project
3. Adjust the ndkPath string in SetNDK.cs
4. Main Menu -> Custom -> Change NDK
5. Make sure Scripting Backend is set to IL2CPP
6. Build
Actual: A dialog pops up stating that NDK cannot be found and asking to locate it
Reproducible with: 2017.4.33f1
Not reproducible with: 2017.4.15f1, 2018.1.0a1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
Comments (3)
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
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Miscellaneous
Dec 23, 2019 00:16
Should maybe mention, I installed 2019 and 2017 installed ontop, might be traces of disaster.
Miscellaneous
Dec 22, 2019 23:48
Fixed my issue (above) I found a download of the NDK dated 15th of Nov 2019 of the 13rb, with the same filename as the one I'm being asked to download (Mac-OSX), but when I change Unity folders to the old unzipped version (with same filename) all seems works.
Miscellaneous
Dec 21, 2019 21:19
With 2017.4.35f1 I get "Unable to list target platforms... ..."
1) pressing download, and installing "android-ndk-r13b-darwin-x86_64" (OSX),
2) when I set the path to this "same" folder I get message: "NDK 26.1.1 is incompatible with IL2CPP. IL2CPP requires r13b (64-bit) (13.1.3345770)." (which was just the one I was redirected to download, right?)
I write it here, since 35f1 release had no real warning and this was the only references (Issue ID).