Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.12.15
Issue ID
1110429
Regression
Yes
[Collab] Pulling changes from project with collab version 1.12.15 to 1.2.9 throws crash exception
Pulling changes from project with collab version 1.12.15 to 1.2.9 throws crash exception. Refer the attached video.
Steps to reproduce:
1) Create new project A
2) Window > Package manager > Unity Collab > Update to 1.12.15
3) Publish the changes.
4) Create new project B
5) Window > Services > Link the project to A
6) Pull the changes
7) In conflicts > Choose theirs
Actual result: Exception in the console.
Expected result: No exception in the console.
Stack trace:
Reload Assembly called from managed code directly. This will cause a crash. You should never refresh assets in synchronous mode or enter playmode synchronously from script code.UnityEditor.Web.JSProxyMgr:DoTasks()
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note:
When it comes to dealing with downgrade scenarios for our package, we will address Editor crashes and similar high-priority issues but ignore warnings and exceptions, as long as they are not spamming any logs.