I am stuck in a bit of an odd place.
I am working in a project that is using UNet on 5.6.0p2 at the moment. We are avoiding the use of SyncVars but are using Cmds and Rpcs for most of our networking needs.
I have recently run into a fairly odd situation that is somewhat hard to describe.
In the Editor.log file I get:
Error building player
(Filename: Line -1)
And nothing else meaningful. The player has not rebuilt. I have scowered the logs and from what I can tell there is nothing meaningful that would indicate why the build has failed.
Worse yet this is from clean, synced back to a point where I could build a week ago in our applications history and coworkers are able to build the project fine at both head and locally. In addition, I can “sometimes” build.
If I remove the references to NetworkManager from the project I can build fine (things of course will not run properly but I can build) If I add the network manager reference back I can “sometimes” build and sometimes the build will fail (mostly fail but I occasionally get a pass). Other people on the team can build fine, yet I cannot.
I am somewhat at a loss to explain the behaviour and have tried all the usual things like nuking the Library folder, a forced fresh resync, reboots etc. In almost all cases I will be able to build and then things will begin to fail and will not.
Reading online in various threads it seems some people have run into size issues with their titles assembly and UNetWeaver / Cecil is unable to properly work with the assembly. There was no indication of why this was the case online. I ran across one user claiming this in a discussion of UniRx and UNet, although there were a couple of threads mentioning this as a potential issue.
When it does not fail I can usually build for a while but switching to a different scene that pulls a reference to the NetworkManager will usually cause a fail, after that all scenes referencing the NetworkManager will fail unless I reboot / force resync and take other drastic measures. (I have not isolated the thing that enables me to build again)
At this point given the one data point I have with the NetworkManager I do suspect this is UNet related and given that the nebulous error messages I have gotten in the past have been from UNetWeaver I am suspicious of that tool.
There is very little to go on, and I am burning time on this without any real idea of what might be the cause.
Any assistance or ideas anyone has would be greatly appreciated.