Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Bug XCode 14.3 breaks my previously working iOS build with double-quote errors

Discussion in 'iOS and tvOS' started by ejoflo, Apr 2, 2023.

  1. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    Apparently my XCode auto-updated last night to 14.3 and now my previously working iOS buid is no longer working. I'm receiving errors like this:

    double-quoted include "UnityAppController.h" in framework header, expected angle-bracketed instead


    Does anyone have a solution to this or is experiencing something similar? I'm on Unity 2021.3.18f1.
    Screenshot 2023-04-01 at 1.51.04 PM.png

    Additional information: I'm building the Xcode Unity project from the Windows version of Unity 2021.3.18f1.
     
    Last edited: Apr 5, 2023
    newguy123 and yolomobile like this.
  2. yolomobile

    yolomobile

    Joined:
    Jan 13, 2023
    Posts:
    3
    Yes Yes Yes. Same issue........
     
    newguy123 and ejoflo like this.
  3. Zatagado

    Zatagado

    Joined:
    Aug 17, 2018
    Posts:
    2
    I am experiencing the same issue on 2021.3.17.
     
    ejoflo and yolomobile like this.
  4. Alexey

    Alexey

    Unity Technologies

    Joined:
    May 10, 2010
    Posts:
    1,602
    are you having "warnings as errors" enabled somewhere? i saw these, but they should be "harmless" warnings
     
    yolomobile likes this.
  5. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    Not that I know of. This is a direct build from Unity 2021.3.18f1. Once I open the XCode file that Unity exports and then try and Build (Play button on XCode), these errors are causing "BUILD FAILED" and my project can no longer be run or built.
     
    philly1164, newguy123 and yolomobile like this.
  6. DrH1gh

    DrH1gh

    Joined:
    May 7, 2017
    Posts:
    2
    Having the same issues with 14.3. I'm suspecting the error is missleading us..and the isue is something else.
    I've tried:
    - pod deintegrate/install again
    - editing my podfile to force IPHONEOS_DEPLOYMENT_TARGET to 12.0 (the same as the Target minimum iOS Version from Unity)

    I can't figure out what it could be.. it was working fine on 14.2
     
    ejoflo likes this.
  7. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    I've installed a copy of XCode 14.2 until Unity provides an update or bug fix. Here's the link if anyone needs to downgrade:

    https://developer.apple.com/download/all/?q=xcode

    You can have both versions installed, I just renamed this one to XCode 14.2. Then when you want to build your iOS project, right click on the Unity XCode project file and choose "Open With > XCode 14.2".
     
    yolomobile likes this.
  8. anthonymedina958

    anthonymedina958

    Joined:
    Apr 4, 2023
    Posts:
    1
    Do 14.2 give support to ios 16.4? I deployed my app 3 days ago and it got rejected because it was crashing on ios 16.4, then I upgraded xcode from 14.1 to 14.3, now it wont work when i click in archive... I readed downgrading to 14.2 would help...
     
  9. AAudrey

    AAudrey

    Joined:
    Apr 4, 2023
    Posts:
    1
    I don't even use Unity but ended up on this thread because I'm getting the same bunch of errors since I upgraded to Xcode 14.3.
    After trying a bunch of things yesterday and loosing my head around it, I decided to go back to Xcode 14.2.
    I don't know what Apple has changed but it definitely smells bad on this version.
     
    ejoflo likes this.
  10. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    My Unity builds with Xcode 14.2 work okay in iOS 16.3.1 which is the latest version on my phone.
     
  11. Alexey

    Alexey

    Unity Technologies

    Joined:
    May 10, 2010
    Posts:
    1,602
    ooooh, i missed "Apparently my XCode auto-updated last night to 14.3" part (i am still on 14.2)
    yeah, you can download 14.2 separately and have it around. I will check on 14.3, sorry for missing this part

    EDIT: works for me with an "empty" project. We need a repro case
     
    Last edited: Apr 5, 2023
  12. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    Just to chime in, I have a copy of Unity-generated Xcode project from 2021.3 branch and it was still compiling just as fine for me with Xcode 14.3. Not sure what the cause is.
     
  13. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    Was it built from the Mac or Windows version of Unity? I'm building from Windows, might make a difference. Not sure.
     
    newguy123 likes this.
  14. ejoflo

    ejoflo

    Joined:
    Sep 15, 2021
    Posts:
    39
    So in general, is it advised to address the "Update to recommended settings" warning in Unity Xcode projects? This is what I've been doing since Xcode 14.2 and I noticed something today. Xcode 14.3 added some new options that are causing the initial bug that I reported:

    Screenshot 2023-04-05 at 10.47.23 AM.png

    Xcode 14.2:
    14.2.png

    Xcode 14.3:
    14.3.png

    When I uncheck 'Target Unity Framework' - Enable Module Verifier, my game is able to be built with Xcode 14.3 and works on my iOS devices. So it appears this isn't a bug, but a "feature" of the new Xcode version.

    In general, which recommend settings should we check when building out a Unity project for iOS?
     
  15. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    The build was done on Mac entirely.
     
  16. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    None of these are mandatory, so it’s best to not adopt the recommendation yourself unless they are required by Xcode or App Store Connect, until Unity clean up their Xcode template (it has lots of old stuff in there)
     
    ejoflo likes this.
  17. DiegoDePalacio_PlayPulse

    DiegoDePalacio_PlayPulse

    Joined:
    Aug 12, 2021
    Posts:
    1
    Hello,

    My app also just got rejected today on App Store Connect because it is crashing on iOS 16.4.

    It's working fine on Android and previous versions of iOS.

    Going to post later if I found something useful.
     
  18. suwawan

    suwawan

    Joined:
    Nov 20, 2015
    Posts:
    1
    Changing "UnityAppController.h" to <UnityFramework/UnityAppController.h> worked!
    Same for the other errors!
     
    Bubinga_Studios, MrMarev and ejoflo like this.
  19. kerem-yokuva

    kerem-yokuva

    Joined:
    Nov 21, 2015
    Posts:
    10
    you mean never.
     
  20. Neonlyte

    Neonlyte

    Joined:
    Oct 17, 2013
    Posts:
    505
    Believe me, if you were to work for any large company, "don't change it if it ain't broke" would be the first motto to go by, as much as we all want the cutting edge stuff. Xcode is the worst offender in breaking changes, but it's Apple, so eventually Unity (and every other company that has their own non-standard build tools) will have to do some fixing.
     
    ejoflo likes this.
  21. FlynnyMac

    FlynnyMac

    Joined:
    Aug 24, 2020
    Posts:
    10
    Any update?
     
  22. batsans

    batsans

    Joined:
    Apr 24, 2023
    Posts:
    1
    "Update to recommended settings" with xcode 14.3 is enabling "a new module verifier"...
    Go to target settings and disable should fix the issue :

    ENABLE_MODULE_VERIFIER = NO;
     
  23. dave_oak

    dave_oak

    Joined:
    Oct 7, 2015
    Posts:
    26
    Thanks batsans, that was the problem for me. For anyone else struggling to find this setting, It's on the Build Settings tab, select Target UnityFramework, the All button to list all build options and type Module Verifier into the search box. There may be a quicker way but this worked for me.
     
  24. Rick66

    Rick66

    Joined:
    Jul 19, 2013
    Posts:
    7
    Thanks batsans and dave_oak, changing this setting in Xcode did the trick for me.
     
  25. dvdfu

    dvdfu

    Joined:
    Sep 1, 2015
    Posts:
    9
    Fixed it for me! Thank you, there were suggestions from other threads that didn't quite work.
     
  26. rmgalante

    rmgalante

    Joined:
    Nov 21, 2009
    Posts:
    59
  27. lanbaug

    lanbaug

    Joined:
    Nov 5, 2019
    Posts:
    4
  28. marcelo_augusto

    marcelo_augusto

    Joined:
    Nov 18, 2018
    Posts:
    11
    Worked for me as well.