- Home /
iOS Building with IL2CPP universal Build causes tons of warnings
I created for testing a completely empty build from scratch with just one simple script attached to the main camera that prints "Hello World".
Despite my best efforts to set all proper settings in unity or XCode I'm getting about 370 of these warnings. What is this about. Can I ignore this ?
"Apple LLVM 6.1 Warning: Integer literal s too large to be represented by a signed integer type, interpreting as unsigned"
"Semantic issue: Comparison of address of UIApplicationLaunchOptionsRemoteNotificationKey not equal to a null pointer is always true"
Value Conversion Issue: Implicit conversion loses integer precision: uintptr_t (aka unsigned long) to uint32_t (aka unsigned int)
The build succeeds, but when I try to submit it to the store I'm getting an error that it's not 64bit or something which I can't give you more details on atm. because there seem to bee connection problems right now with XCode
XCode 6.3.2 Unity 4.6.5f1
The Warnings in XCode:
Few days ago I've updated Unity to 5.1.1 and had few successful builds with no errors (Xcode 6.3.2). But yesterday it'd started producing these tons of errors. I've tried building from old successful projects archives — same problem. I build virgin project — the same.
I've not changed anything, it started from nothing.
It's not an unswear, but I'll update if I dig something.
I've installed patch 5.0.3p3 (over 5.1.1p1, I did not notice that it would be downgrade) and my 5.1.1p1 project compiled without errors (and did not change its version label)
Has anybody been able to resolve this? I am stuck and extremely frustrated
This error also breaks my game
I'm using version 5.0.3p3. Xcode builds and runs on iPhone without these warnings, but when I archive projects all of them appear again. But Xcode validates archive and allows to upload it to AppStore.
Answer by Viperia · Jun 10, 2015 at 03:31 PM
Now, it works for me: i already have warnnings but submission id ok.
(in xcode)
Just go to Build setting -> architectures -> "Standard architectures (arm7, arm64) -$(ARCHS_STANDARD)"
And Build Active Architecture Only -> Debug = Yes; Release = No
Answer by gamepat · Jun 11, 2015 at 09:05 AM
So I tested my game that has these warnings on armv7s and arm64 devices and everything seems fine, so I guess these warnings can be ignored for now.
Concerning the error that I got when submitting to the app store, I found a solution on another thread. I just had to unplug my iPhone 5 before clicking Archive :) ... has to do with the device not being a arm64. I guess it could be changed too by setting "Build Active Architecture Only" to "No", but just to be sure ;). If you encounter a similar problem, I'd give it a try.
No settings that I played around with seemed to change the thing with the warnings for the better.
I too get 426 warnings that I never got before 64 bit was required. Bulk_mscorilb_6.cpp Apple LLV$$anonymous$$ 6.1 warning Bulk_mscorlib_0.cpp Value Conversion issue and many more... I updated all my software including the latest xcode and Unity 5.1.1 Set build settings in Unity to Scripting Backend IL2CPP Architecture to Universal Run in xcode as Release Had no choice but to send to itunes connect has is... Will post results when I know more a little dishearting to say the least.
SO FRUSTERATING Still doesn't work with all the great insights
I have all these settings as per this thread and i still get the same 64 bit support error when i try to upload the archive.
Answer by Bentoon · Aug 02, 2015 at 07:42 AM
Latest UnityBuild & Latest xCode seem to play together better
Your answer
Follow this Question
Related Questions
Unity www class crashes on iOS 64 bit 2 Answers
What to do with "Undefined symbols for architecture ..." in Xcode for IL2CPP project? 0 Answers
Undefined symbols for architecture armv7 - Unity XCode Project Error 0 Answers
Strange behavior while running in Xcode: error only when "Development Build" is unchecked 0 Answers