Search Issue Tracker
Fixed in 2019.1.X
Votes
1
Found in
2018.3
2018.3.0f2
Issue ID
1115733
Regression
No
Project building fails when using EditorApplication.LockReloadAssemblies() on .NET 4.0
Reproduction steps:
1. Open the Project inside of the "BuildFailRepro.zip"
2. Build the Project as Windows 86x64
3. After the Build completes Build the Project again
Expected: Build completes successfully
Actual: Build is interrupted by an error - Copying assembly from 'Temp/Assembly-CSharp-firstpass.dll' to 'Library/ScriptAssemblies/Assembly-CSharp-firstpass.dll' failed
Reproduces on: 2018.3.3f1
Does not reproduce on: 2019.1.0b1, 2019.2.0a2
Could not test on 2017.4.19f1 due to project errors
Note:
- Sometimes the Project does not build even on the first time
- Obfuscator plugin inside the Project is the one that uses EditorApplication.LockReloadAssemblies(), when the package is disabled, this issue does not persist
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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Resolution Note (fix version 2019.1):
This is fixed for future versions (2019.1.0b1 and above). We are sorry to report that a backport will be unavailable for this specific issue. This is due to the fix happening through a separate change to the code base. An upgrade to 2019.1.0b1 will fix this problem.