Search Issue Tracker
By Design
Votes
0
Found in
5.2.3p2
Issue ID
750709
Regression
No
Project doesn't play with "UNetWeaver error: Exception :System.ArgumentException: An element with the same key already exists.."
Reproduction steps:
1. Open and play attached project with 5.2.3p2 version of unity (reproduces with any scene).
Actual result: project doesn't start because of errors:
Expected result: project start as usual.
(5.2.0p1, 5.2.3p2)
UNetWeaver error: Exception :System.ArgumentException: An element with the same key already exists in the dictionary.
at System.Collections.Generic.Dictionary`2[System.UInt32,System.UInt32].Add (UInt32 key, UInt32 value) [0x0007e] in /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/Dictionary.cs:404
Failure generating network code.
UnityEditor.Scripting.Serialization.Weaver:WeaveUnetFromEditor(String, String, String, String, Boolean)
Additional notes:
* Might be related to case 701313.
* Could be caused by lambda expressions.
* Project doesn't work on 5.3.0f4 after API update.
* Might be fixed in 5.3.0f4.
* After cleaning up more than half scripts with 5.1.4p1 to start the project, issue disappears. But it doesn't reproduce on new versions either. Not sure if this is a regression.
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
IndieGa
Feb 21, 2016 00:33
We had the same error, and it is really a compiler error. We found that if the Assembly-CSharp.dll larger than 1 MB is not possible to read it. That is, when the amount of code that is greater than a threshold, the library is compiled crooked. So now we use this https://bitbucket.org/alexzzzz/unity-c-5.0-and-6.0-integration/overview. Eeverything works fine. I hope this helps someone. Good luck!
ZimM
Feb 20, 2016 19:56
How could this be by design? This is a bug in Mono compiler:
https://github.com/jbevain/cecil/issues/241
kyubuns
Feb 17, 2016 23:55
I have same problem.
Why is the issue priority 2??
I cannot develop our product because of the issue.