- Home /
Unity 5's xCode build..... SUCKS?
I am having trouble getting almost everything in unity 5 to run right.
It got to the point where I made an empty scene, just to build it and get it to run in xcode. That empty scene gave me SIX HUNDRED AND EIGHTY ONE ISSUES. 681, folks.
What on Earth caused this?? How the... HECK does that happen with an empty scene? I'm not only shocked but DISGUSTED. Somebody please make sense of this for me. I'm sharing a screen shot of what happened. This has literally floored me. Keep in mind: the scene is EMPTY.
I cannot be the only person shocked by this. Why does this happen??
Build speed tips: set DEBUG_INFOR$$anonymous$$ATION_FOR$$anonymous$$AT to just dwarf, and set ONLY_ACTIVE_ARCH to YES. This could reduce build times by half.
Answer by Tekksin · Jul 27, 2015 at 07:12 PM
Okay, in the build settings in unity, set the Scripting Backend to Mono 2x. Phew. Everything's back to normal. I really hope the new ll2cpp is not necessary for new apps on ios. I can't stand it, already.
IL2CPP is 100% necessary, for new apps as well as updates. New apps had to be 64-bit in January, and the deadline for updates being 64-bit was June. You can't use $$anonymous$$ono for any builds you intend to put on the store. But those are warnings, not errors; don't give yourself a heart attack. Ideally Unity would clean that up at some point so there would be 0 warnings just for the sake of tidyness, but they don't affect anything.
That is the saddest news I have ever heard in my entire life.
Your answer
Follow this Question
Related Questions
Lots of "semantic issues" causing build to fail? 0 Answers
Blending XCode Builds 0 Answers
Xcode build fails, How to ? 1 Answer
Error on build since upgrading to unity 5 1 Answer
Wrong version of Unity opening 1 Answer