I am getting 23 issues when building for iOS (Unity 4). This is a clean build, after deleting the Build folder.
Should I worry about them? Should I change something?
Unity iPhone (22 issues):
iPhone_Sensors.mm Deprecations:
/Users/db/Developer/unity/Teddy/Build/Classes/iPhone_Sensors.mm:347:53: ‘locationServicesEnabled’ is deprecated: first deprecated in iOS 4.0
Dependency Analysys Warning (several like this):
Warning: no rule to process file ‘$(PROJECT_DIR)/Icon@2x.png’ of type image.png for architecture i386
Dsymutil Warning (several like this):
(null): warning: (i386) /Users/db/Developer/unity/Teddy/Build/Libraries/libiPhone-lib.a(CharacterController.o) object file doesn’t contain DWARF debug information
"Missing “Default-568h@2x.png” - does Unity 4 not fully support iPhone 5 yet?
“PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE, but used in method_addresses from /Users/jay/Library/Developer/Xcode/DerivedData/Unity-iPhone-cmdrajikwnsoatbkpzmmwpfnnqxr/Build/Intermediates/Unity-iPhone.build/Debug-iphoneos/Unity-iPhone.build/Objects-normal/armv7/Assembly-CSharp-firstpass.dll.o. To fix this warning, don’t compile with -mdynamic-no-pic or link with -Wl,-no_pie”
Apart from the above - which I don’t understand - these warnings seem pretty benign, but call me old fashioned, I like zero errors and zero warnings in my builds
I’m not sure these warnings are that benign. Our game was rejected by Apple today as it is crashing on launch of iPhone 5 and iPad (3rd generation). Built with Unity 4 with iOS standard. (It works perfectly on iPhone 4 / 4s and iPad 2 test devices)
The warnings you posted are the only warnings that I am getting. The crash report from Apple indicated that an object that was being referenced was missing (as far as I can tell based on searches):
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000
I made a new build with a blank scene to see if there was something wrong somewhere else in the game but the same errors arise in Xcode when doing an analysis.
"SplashScreen.mm
‘Classes/UI/SplashScreen.mm:30:9: Incorrect decrement of the reference count of an object that is not owned at this point by the caller’
(void)unloadImage;
{
if(self.image)
{
[self.image release];
self.image = nil;
}
}
1.Property returns an Objective-C object with a +0 retain count
2.Incorrect decrement of the reference count of an object that is not owned at this point by the caller "
etc.
Does this mean the only option is to upgrade to Unity Pro and iOS Pro to add the "Missing “Default-568h@2x.png” ?
If anyone finds any way around this or could shed any light I’d be really grateful…
I was going to start a thread on these exact problems, but here we are!
I’m getting all of these: 5 Dysmutil warnings, Retina 4 Support Missing, iPhone_Sensors.mm Deprecations; I’m also getting an Apple Mach-O Linker warning. Is there something wrong with Xcode, our projects, or is Unity 4 in need of an update? I didn’t have any of these problems with 3.x.
Binarie, I don’t think upgrading is going to solve your problem, as I’m using Unity Pro and iPhone Pro and I get the same warning. The strange thing is that XCode tells me that my iPhone 5 splash screen is missing but when I click to fix the problem it says that the image already exists! Replacing it doesn’t make the warning go away, but it does replace your splash screen with a flat black image.
I’m a bit concerned because I want to submit a build in the next couple of days and I’m not sure how these warnings could affect the process.
And I’m with you Ecc83! I feel much better having 0 warnings in my build even if the warnings are harmless!
There goes my best excuse for upgrading to pro versions…thanks Horror!
That was my last resort that would work to fix this though so it obviously is a serious bug between Unity 4.0 and Xcode 4.5. I sent a message to Mantis pleading for help as we’re hurtling towards the app review team’s break from the 21st to the 28th of December. If I hear back I’ll post here to let you know if there’s anything that can be done or if we have to wait for an update…
Has anyone experienced crashes on launch from this issue when testing on an iPhone 5 or iPad 3 (or later)?
I do not want to take this thread off course, but I can say that after upgrading from Unity 3.5 to UNity 4 (basic) my game crashed on the device constantly at random places. I was unable to figure out why, as I did not get anything useful in the console.
This crash is detailed in this forum thread but eventually, I downgraded back to 3.5 and everything is smooth again…
Recently I read too many threads and Unity Answers posts about rejected Unity builds.
It would be nice if someone from Unity can comment on the original warnings question.
Ok, so the warnings won’t cause an issue so long as you don’t touch anything in Xcode. If you add the missing retina image using Xcode it will corrupt the build and crash on launch so make sure to leave it alone. Our app was approved following a fresh build. I didn’t do anything to fix any warnings.
One other thing which I was advised not to touch was ‘Main Interface’ in Xcode. I had selected ‘Main Window’ as I was following the guide from Xcode to publish the app. This will also cause an error so you need to leave it blank.
"Missing “Default-568h@2x.png”
in Xcode,find the Target and Summary field, delete the Retina-4 inch picture,and select it again…
about the deprecated thing ,replace it like
//return gLocationServiceStatus.GetLocationManager().locationServicesEnabled;
return [CLLocationManager locationServicesEnabled];
I am not sure is this ok or cause any other problem… X)
now,just some "dsymutil warning " left ~ is there anyone tell me how to remove them ?
In Xcode, select your project (normally Unity-iPhone or something) in the upper left and then select your target. Go to the “Build Settings” tab, and scroll to the section titled “Apple LLVM compiler 4.1 - Code Generation.” There is a row titled “Generate Debug Symbols.” Expand this row and you should see Debug set to Yes and Release set to No. Set Debug to No, and the compiler warnings will disappear.
Hi, I have also issues with upgrading to unity 4 and xcode 4.6, im getting this in xcode :
ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE, but used in method_addresses from /Users/amitchai/Library/Developer/Xcode/DerivedData/Unity-iPhone-dqvzjbozlulizbedqspaftdsyhnc/Build/Intermediates/ArchiveIntermediates/Unity-iPhone/IntermediateBuildFilesPath/Unity-iPhone.build/Release-iphoneos/Unity-iPhone.build/Objects-normal/armv7/UnityEngine.dll.o. To fix this warning, don’t compile with -mdynamic-no-pic or link with -Wl,-no_pie
horrible one. i can get rid of this by building unity with ios4, but this cause other problams…
Just for the test i build clean and empty unity project and still getting this PIE error. ??? anyone?
