Search Issue Tracker
Fixed in 2019.1.X
Votes
1
Found in
2017.3.0b11
Issue ID
974227
Regression
No
Setting SDK to incorrect path, doesn't show any warning
How to reproduce:
1. Create a new project
2. Go to Preferences > External Tools
3. Cut Android SDK path
4. Click on Browse and choose incorrect folder
Result: Warning that SDK doesn't exist there is not provided and same window just reopens
Expected result: User should see a warning that folder is incorrect
Note: NDK and JDK shows a warning
Reproducible: 5.6.4f1, 5.6.4p3, 2017.1.2p3, 2017.2.0.p3, 2017.3.0b7, 2017.3.0b11, 2018.1.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Add comment