Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0f2
2017.3.0f3
Issue ID
982271
Regression
Yes
Editor assemblies get referenced in main and Plugins projects
To reproduce:
1) Open attached project
Expected: No warnings in console
Actual: Console has warnings about type confliction like this:
Assets/ConsolePro/Remote/LiteNetLib/INetEventListener.cs(75,42): warning CS0436: The type `FlyingWormConsole3.LiteNetLib.INetEventListener' conflicts with the imported type of same name'. Ignoring the imported type definition
If it doesn't reproduce immediately, create a new script to force scripts to recompile.
Reproduced in 2017.3.0f2, 2017.3.0f3, 2017.3.0p2
Not reproduced in 2017.3.0f1
Cannot test 2018.1 because the project crashes there no matter the specific version
Comments (1)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
nflodin
Feb 06, 2018 10:18
We noticed this when the compiler complained that in the facebook api; FB is defined in multiple assemblies. Turned out it was defined in Facebooks assembly Facebook.Unity and Facebook.Unity.PlatformEditor.
Thought this would be good info if someone were to google this :)