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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in version 2 beta 3 (Fixed in Hub version 2.0.0)