Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b2
Issue ID
905623
Regression
Yes
The type or namespace name `UnityEditor' could not be found when trying to build asset bundle or standalone player
Reproduction steps:
1. Open project attached (New Unity Project 145.zip) or unitypackage (BundlesError.unitypackage)
2. Press on "Test/Build Bundle".
Expected result: Bundle will be built.
Actual result: Bundle will not be built, since scripts had compiler errors. Errors:
"The type or namespace name `UnityEditor' could not be found. Are you missing an assembly reference?"
"Error building Player because scripts had compiler errors"
Notes: Scripts from "https://docs.unity3d.com/ScriptReference/BuildPipeline.BuildAssetBundles.html" works fine.
Reproduced on: 2017.1.0a2, 2017.1.0b2.
Works fine on: 5.4.4p4, 5.5.3p1, 5.6.0p3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
- Warning "Item m_LightProbeSystem not found in window PC_RPAsset" logged when navigating to RP Asset from Probe Volume Component
- Tessellation has poor performance in URP when rendered using Metal
Add comment