Search Issue Tracker

Fixed in 5.4.2

Votes

5

Found in

5.4.0b15

Issue ID

793624

Regression

Yes

Unity does not include UnityEditor.iOS.Xcode in project file

iOS

-

How to reproduce:

1. Open a new project
2. Create a script and place it in a folder named 'Editor'.
3. Add "using UnityEditor.iOS.Xcode;" to the top of the script
4. Add "PBXProject project = new PBXProject();" to the Start() message
5. Save and switch back to Unity
- Note that Unity compiles the code successfully, but in the editor the code is displayed in red

- Reproduced in Version 5.4.0b17 (d34aa569a642), Version 5.3.4p4 (43a3882ae25c)
- Not reproducible in Version 5.2.4f1 (98095704e6fe)

Comments (36)

  1. Bart-S

    Aug 22, 2017 09:50

    Still having this issue in monodevelop when using Unity 5.6.1p1 Not in Rider though.

  2. QubixGames

    Jul 19, 2017 11:19

    occurs also in 5.6.2f1

  3. BenoitFreslon

    Jul 11, 2017 14:42

    Workaround from @ETHAN_VISUALVOCAL

    Workaround for MonoDevelop:
    In MonoDevelop, go under "Project" menu > "Edit References..." > ".NET Assembly" tab > Click "Browse" in lower right, and browse to your Unity install to find the dll, e.g. "/Applications/Unity/PlaybackEngines/iOSSupport/UnityEditor.iOS.Extensions.Xcode.dll"

  4. jackalkane

    Jun 16, 2017 05:07

    Thanks VAN800. I was able to get your Rider code working in my project and it's fixed the issue so that I can at least run the game and it imports the dlls now automatically. This will save me tonnes of hours.

    Undoubtedly though this is still a bug with Unity. My guess is that it has something to do with the way it detects the DLLs and I think it started after I updated Xcode back in December of last year.

  5. jackalkane

    Jun 16, 2017 04:32

    *still an issue on 5.6.1f1

  6. jackalkane

    Jun 16, 2017 04:32

    This is still an issue. And worse yet, it occurs every single time I open Unity and I have to repeat the steps for my previous post by deleting MonoDevelop settings and resetting it, checking it manually, and then about an hour later having to do the same thing. It's extremely frustrating.

  7. MASTware

    May 26, 2017 19:59

    Same issue with full installation of Unity v5.6.1f1 under Mac OS Sierra 10.12.5 and XCode 8.3.2.

  8. jackalkane

    Jan 05, 2017 06:12

    I also had the same problem in 5.5.0f3. I tried what ETHAN_VISUALVOCAL recommended on the comment from 10/13 (kudos) but ran into a problem where I couldn't edit the references initially in MonoDevelop because the option was grayed out. I ended up having to clear out the MonoDevelop settings completely and relaunching it which immediately fixed the problem. Then I did ETHAN's fix and got it in there.

    Running macOS Sierra (10.12.2)
    Unity 5.5.0f3
    MonoDevelop 5.9.6
    Xcode 8.0 (8A218a)

    I've been running Unity and MonoDevelop on this same PC for at least 3 years so it's possible a bug was created from patching the same install repeatedly instead of starting fresh.

  9. breban1

    Nov 24, 2016 03:52

    The fix from @ETHAN_VISUALVOCAL from OCT 13, 2016 22:19 worked for me!

    Thanks SO much for the "fix"!

  10. aditya

    Nov 22, 2016 12:14

    For me adding UnityEngine.iOS.Extensions.Xcode.dll as reference in monodevelop along with UnityEngine.iOS.Extensions.dll worked ... i think you need to reference both of them to work

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.