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
- Scrollbar in "My Assets" detail window appears compressed/cut off
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
Add comment