Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.2.X, 2018.3.X
Votes
2
Found in
2017.3.1p4
Issue ID
1018716
Regression
Yes
UnityEditor.iOS.Xcode is not found when running editor in batch mode
To reproduce:
1. Open project
2. Launch Unity with the batchmode and quit option :
-projectPath <ProjectPath> -logFile <ProjectPath /log1.txt> -batchmode -quit
3. Open 'log1.txt'
4. Notice that Xcode does not exist in UnityEditor.iOS namespace:
-----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-Editor.dll
Compilation failed: 1 error(s), 0 warnings
-----CompilerOutput:-stderr----------
Assets/Editor/XprojUpdater.cs(4,27): error CS0234: The type or namespace name `Xcode' does not exist in the namespace `UnityEditor.iOS'. Are you missing an assembly reference?
-----EndCompilerOutput---------------
- Finished compile Library/ScriptAssemblies/Assembly-CSharp-Editor.dll
Assets/Editor/XprojUpdater.cs(4,27): error CS0234: The type or namespace name `Xcode' does not exist in the namespace `UnityEditor.iOS'. Are you missing an assembly reference?
Reproduced: 2017.1.0p5, 2017.1.3p2, 2017.2.2p1, 2017.3.2f1, 2017.4.1f1
Not reproducible 2017.1.0p4, 2018.1.0b1, 2018.1.0b11, 2018.2.0b2
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
LASK
Jun 14, 2018 10:02
I have the same issue on 2017.1.3f1. Is there any workaround?