Search Issue Tracker

Won't Fix

Votes

2

Found in

2017.3.0f3

Issue ID

1000081

Regression

No

"UNet" unable to serialize parameters from Assembly Definitions

Scripting

-

Reproduction steps:

1. Open "TestAsmDef.zip" project

Expected Result: No errors appear/ everything is properly serialized
Actual Result: "UNetWeaver" errors appear

Reproduced with: 2018.2.0a1 (f0f622), 2018.1.0b7, 2017.3.1p1, 2017.2.1p4, 2017.3.0b1, 2017.3.0a2 (fa0da2)
Did not reproduce on: 2017.3.0a1, 2017.2.1p4 (Assembly Definitions only implemented from 2017.3.0a2)

Note:
"UNetWeaver error: parameter [DataObject] is of the type [DataObject] is not a valid type, please make sure to use a valid type."
"UNetWeaver error: GetReadFunc unable to generate function for:DataObject"
"UNetWeaver error: ProcessNetworkReaderParameters for OtherCustomAssemblyComponent:RpcDoSomething type DataObject not supported"
"Failure generating network code."

  1. Resolution Note:

    Using external assemblies is not supported and as UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.

    If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.

Log in to vote on this issue

Comments (1)

  1. Arkade

    May 06, 2018 21:47

    Believe I've just run into the same problem.
    Unity 2017.03.01p4
    A struct in asmdef 1 which is used as a parameter to a Command in asmdef 2 (which depends on asmdef 1).
    Workaround: Move the struct to asmdef 2. Structurally it's incorrect but it'll do for now.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues