Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.1
2020.2
2020.2.0a19
Issue ID
1266377
Regression
No
[Reflect] Standalone build fails with package errors if Unity Reflect is installed
Standalone build fails with Package errors when Unity Reflect package and projects are imported. Build fails even when Unity Reflect package is installed in an empty project. Refer the attached video
Steps to reproduce:
1) Create a new project
2) Window > Package Manager > Install Unity Reflect
3) Window > Reflect > Reflect Window
4) Update / Import project
5) File > Build Settings > Build for Standalone
Actual result: Builds fails with package errors
Expected result: Build should be completed successfully
Occurring in: 2020.2.0a19, 2020.1.0a1, 2020.1.0f1, 2020.1.0a1 with Reflect version 1.2.0-preview.26, 1.0.0-preview.11
2019.4.8f1 with package version 1.2.0 preview.26
Stack trace:
Library\PackageCache\com.unity.reflect@1.2.0-preview.26\Runtime\Utils\LoginResolver.cs(510,33): error CS1069: The type name 'Registry' could not be found in the namespace 'Microsoft.Win32'. This type has been forwarded to assembly 'Microsoft.Win32.Registry, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Consider adding a reference to that assembly.
Environment: Both 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
- [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
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note:
Currently the only Unity version officially supported by Reflect is 2019.3 (see documentation). The above bug reports used 2020.x which is not supported yet