Search Issue Tracker
Fixed
Fixed in 2020.3.38f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b4, 2023.1.0a2
Votes
0
Found in
2019.4.38f1
2020.3.34f1
2021.3.1f1
2022.1.0f1
2022.2.0a11
Issue ID
UUM-931
Regression
No
UWP Build & Run picks the wrong instance of Visual Studio to build when there are multiple installed
How to reproduce:
1. Install Visual Studio 2022 with all the required components for UWP;
2. Install Visual Studio 2022 Preview without required components for UWP;
3. Build & Run any project to UWP from Unity
Expected results: Build is successful
Actual results: Build fails with errors
Reproducible with: 2019.4.38f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment