Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
Issue ID
986267
Regression
No
Android device selection functionality is broken when Android SDK path is not specified
To reproduce the issue:
- Go to Unity Preferences -> External Tools and delete Android SDK path
- Go to Build Settings and choose Android platform
- Notice that no run devices are displayed and console is spammed with error messages (might need to hit Refresh button if doesn't reproduce correctly)
Run Device section should show some message informing that Android SDK is unavailable or ask user to select SDK path.
Also I think that AndroidSDKTools.GetTools() should only be callable from UI thread only because it might ask user to specify SDK path. When it gets called from worker threads bugs like this happen. This might require reworking IDeploymentTargetsExtension and some other places.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment