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
- Unused Particle System Renderer Mesh settings cause performance degradation when calling SetActive
- Project Browser shows the Asset folder empty when Select Dependencies is clicked without any asset selected
- Export as JSON and CSV options missing from the Quick Search save feature
- Crash on IMGUI::GUIWindow::OnGUI when rendering scene view window in play mode in a specific project
- "FileNotFoundException" & "IOException" thrown when adding "User" Index after deleting "Assets" Index in Search Index Manager window
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