Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.0 - preview.17
Issue ID
1216924
Regression
Yes
Errors are thrown in the Console window when Collaborate package is installed
How to reproduce:
1. Create and open a new project
2. Open the Package Manager
3. Install Unity Collaborate package
Expected result: no errors are thrown
Actual result: errors are thrown
Reproducible with: 2020.1.0a17, 2020.1.0a25, 2020.2.0a1 (2.0.0 - preview.6, 2.0.0 - preview.8, 2.0.0 - preview.15, 2.0.0 - preview.17)
Not reproducible with: 2018.4.18f1, 2019.3.3f1, 2020.1.0a16 (2.0.0 - preview.6, 2.0.0 - preview.8, 2.0.0 - preview.15, 2.0.0 - preview.17)
Could not test with: 2017.4.37f1 (Package Manager not available)
Thrown error: Library\PackageCache\com.unity.collab-proxy@2.0.0-preview.17\Editor\Client\Bootstrap.cs(21,13): error CS0103: The name 'JSProxyMgr' does not exist in the current context
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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note:
Min supported version for package is implemented for released packages but not for preview builds. Upgrading to v1.3 or v2.1 of Collaborate when running Unity 2020.1+ will remove these errors.