Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
1
Found in
2020.1.0b12
Issue ID
1256617
Regression
No
Unity is trying to detect android sdkmanager in a wrong path when using SDK installed with Android Studio 3.6.1
Steps to reproduce:
1. Install Android Studio 3.6.1
2. Install Andoid SDK using it
3. Open Unity
4. Set platform to Android
5. Under Unity > Preferences ... > External Tools uncheck "Android SDK Tools Installed with Unity (recommended)
6. Select the path of SDK you just installed using Android Studio 3.6.1
7. Try to Build & Run
Expected Result: Unity detects all the required tools and uses that SDK
Actual Result: Unity is trying to detect SDKMANAGER in
"/Users/${USERNAME}/Library/Android/sdk/cmdline-tools/latest/bin/sdkmanager"
when it actually is in
"/Users/${USERNAME}/Library/Android/sdk/cmdline-tools/latest/tools/bin/sdkmanager"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Particle is not visible in RenderTexture when Renderer's material is set to Default-Particle and Camera's BG Alpha is set 0
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
Add comment