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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment