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
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
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
- Physics and Raycast have different behavior when enum is exposed in the Editor
- TextField's text is mixed up and overlapping when "Noto Sans-Display" font is used
- TutorialManager Warnings are thrown when creating Test Track, LEGO or 2D Platform microgame template projects
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 :)