Search Issue Tracker
Not Reproducible
Votes
1
Found in [Package]
0.1.0
Issue ID
1146230
Regression
Yes
Error of copying assembly appears after installing memory profiler package when Multiplayer HLAPI package is installed
To reproduce:
1. Open attached project
2. Install multiplayer HLAPI package is it's not installed
3. Go to the package manager and uninstall memory profiler
4. Install again package memory profiler
5. Check the console for the error
Actual result: Console throws error:
Copying assembly from 'Temp/com.unity.multiplayer-hlapi.Runtime.dll' to 'Library/ScriptAssemblies/com.unity.multiplayer-hlapi.Runtime.dll' failed
Expected result: There should be no error.
Reproduced in: 2019.1.0a11; 2019.1.0f2; 2019.2.0a11
Not reproducable in: 2018.3.13f1 because there is no multiplayer HLAPI package; 2019.1.0a10
Comments (2)
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
samra2494
Jul 10, 2019 07:24
yes it works... thanks a lot OLABRAHAMMAR
, remove the file
Library/ScriptAssemblies/com.unity.multiplayer-hlapi.Runtime.dll
and now build works again, once only. The file-removal procedure has to be repeated for every build
OlaBrahammar
Jun 03, 2019 08:27
Workaround:
This bug is preventing me from building (PC/Win), but i have found a workaround; close Unity editor, remove the file
Library/ScriptAssemblies/com.unity.multiplayer-hlapi.Runtime.dll
and now build works again, once only. The file-removal procedure has to be repeated for every build