When trying to build to iOS with the latest Unity 5.2.1p3 patch, the build fails in Xcode with the following error:
clang: error: invalid deployment target for -stdlib=libc++ (requires iOS 5.0 or later)
It will fail with that when trying to build with iOS target 8.2, 8.3, 8.4, and 9.0. If you walk your target back to 8.1, it will work.
Reporting this mainly to alert Unity and/or see if anyone else is running into this.
Anyone else having issues with this? Still a problem with all the latest updates from today (new Unity 5.2.2, new Mac OS X El Capitan 10.11.1, new Xcode 7.1, new iOS 9.1)
Yes having same issue. I’m on Yosemite, Xcode 7.1, Unity 5.2.2). The player settings don’t appear to be carrying through to the Xcode build, and even when I change them manually in Xcode, still getting the error →
invalid deployment target for -stdlib=libc++ (requires iOS 5.0 or later)
How would I report this? I’ve never reported a bug to Unity before, but would be happy to help.
You should just click Help → Report a bug in Unity Editor menu and it will launch bugreporter.
Hi
Sorry to ask. Did you raise a big and if so do they hold links on the site to view progress anywhere? I’m having the same issue 
I did report the bug, but not convinced it’s been addressed. I checked the Patch 5.2.2p3 and the issue still exists. If you try to build for anything higher than 8.1, the issue shows up. From 8.2 on up to past iOS 9, when you build you’ll get the Xcode project defaulting to iOS 4, so the iOS build settings are not be relayed to the Xcode project from Unity. If you back off to iOS 8 or 8.1 for the build target it will pass the settings over and if you not using Unity Cloud build, you can then just manually go into your Xcode project and bump up the build target to higher iOS 8.4 or 9+. If you’re using Unity Cloud Build what I found was that whenever if fails to pass the settings over to Xcode and does the iOS 4 default, then Cloud Build fails and it doesn’t override the build target to the on specified in the web interface. Hope this helps those of you out there to run into this issue, and hopefully the issue gets fixed at some point.
Hi, we are aware of the issue. The fix is expected in 5.2.3p1.
5.2.3p1 same issue
5.2.3p1 is not out yet…
was this fixed? i’m seeing the same problem with Unity 5.2.2p4… I don’t think this was the case with 5.2.1p4
The issue is still in Unity 5.2.3p3 …