Search Issue Tracker
Not Reproducible
Votes
0
Found in
2020.1.0a22
Issue ID
1217763
Regression
Yes
Installing Androids SDK's when a project is open leads to incorrect pathing of the Androids SDK's
To Reproduce:
- Open unity with the Android module installed from the hub - "Android Build Support" BUT NOT the "Android SDK & NDK tools" installed
- Go to build settings - (File -> Windows -> Build Settings)
- Switch to android - (click Android -> Switch Platform)
- Build and Run
- Expected errors of no SDKs shows in console
- Go back to the hub and install the Android SDK's
- Go back to build and run in the project
Expected Result:
a build goes to android and no errors appear in the console
Actual Result:
Errors in console ("Unable to install APK to device") - the SDK's don't seem to link properly with a project open
Reproduceable Versions:
2020.1.0a22, 2020.1.0a21, 2020.0a12
Unreproduceable versions:
2018.4, 2019.1.13f1, 19.3.0b7, 2020.1.0a3, 2019.3.0f3, 2020.0a11
Tested on Windows and MAC
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment