Search Issue Tracker
Fixed
Votes
0
Found in
2019.2.0a7
Issue ID
1138396
Regression
Yes
[HUB] Installed build targets are not shown while opening an existing project
Installed build targets are not shown while opening an existing project.
Steps to repro:
1. Install unity with any build target. (Android, iOS, WebGL etc.)
2. Create a new project.
3. Close unity editor.
4. Open HUB.
5. Open 'Advanced Open' window for the newly created project.
6. Click on installed build targets.
Actual Result:
Installed build targets are not shown
Expected Result:
Installed build targets are shown.
Reproducible on:
2019.2.0a9, 2019.2.0a7
Works fine on:
2019.2.0a6, 2019.1.0b8
Environment:
Windows and MAC
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
Fixed in version 2 beta 3 (Fixed in Hub version 2.0.0)