Search Issue Tracker
Fixed in 1.0.6
Votes
1
Found in [Package]
1.0.2
Issue ID
1152421
Regression
Yes
[UNET] Runtime.dll fails to move on upgrading project from 2019.1
Runtime.dll fails to move on upgrading project from 2019.1
Steps to Repro:
1. Create a new Project with 2019.1
2. Download and import Tanks! Tutorial project from the asset store
3. close and open the project with 2019.2.0b2
Alternative Steps to reproduce the issue (reproduced with version 1.0.4):
1. Create a new empty project
2. Open package manager
3. Reset packages to default
4. Uninstall unity collab
5. Install Multiplayer HLAPI
6. Install XR Legacy Input Helpers
Actual Result:
Multiplayer package fails to upgrade gracefully
Expected Result:
The package is updated gracefully and no errors appear in the console
Occurring with:
2019.1.14f1, 2019.2.0a13, 2019.2.1f1, 2019.3.0a12
Working with:
2019.3.0a2, 2019.2.0a12
Environment:
Windows Only
Stack Trace:
Copying assembly from 'Temp/com.unity.multiplayer-hlapi.Runtime.dll' to 'Library/ScriptAssemblies/com.unity.multiplayer-hlapi.Runtime.dll' failed
-
samra2494
Jul 10, 2019 07:25
, 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
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
- Graphics Settings RP Asset is changed to None when you press the Escape Key in Object Picker and choose to Continue
- Dedicated Server player crashes on complex HDRP project
- [Mac] Dedicated Server build only decreases Memory usage, CPU time and Build size remain the same as Standalone
- [Linux][Mac] Executing Build And Run with Dedicated Server platform does not open Terminal
- [deprecated] BuildOptions.EnableHeadlessMode needs clearer warning for its conflicts with BuildOptions.subtarget field
Resolution Note (fix version 1.0.6):
Closing since UNet is deprecated and this seems like low priority issue. It should only happen once and only when upgrading older projects in 2019.x. Package is automatically added in this upgrade flow, this will no longer happen in 2020.1. It's safe to remove from the manifest or package manager if it's not being used. Reopening editor should also get rid of the issue. If it's still a problem it can be worked around by embedding the package and editing WeaverRunner.cs OnCompilationFinished function, adding this at the top:
if (targetAssembly.StartsWith(“Unity”))
return;