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
Comments (1)
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
LASK
Jun 14, 2018 10:02
I have the same issue on 2017.1.3f1. Is there any workaround?