"Base SDK Missing" every single time

Unity Engine
,
1

I’m evaluating UnityPro iOS using the latest non-beta XCode (3.2.5) and every single time I go to “Build and Run” from Unity, the SDK in the XCode project gets reset to “iOS 3.2 (missing)” and the Target is “iOS 2.2” or something nuts, and has to be changed in two places, then a random change made to the build settings (eg change to Debug then back to Release) before I can get a “Latest iOS (current 4.2)” build.

This is driving me completely crazy!

I read a tip that said I should try setting the iOS SDK version within Unity to be “Unknown” but this does not help.

Is Unity iOS really as broken as it appears? How can I make the build process sane so I can keep my hair?

2

First of all it is known xcode issue with “Latest iOS (current 4.2)”
http://developer.apple.com/library/ios/#releasenotes/General/RN-iOSSDK-4_2/index.html

The issue is - you are using 3.1, right, that was created before ios sdk 4.2 (iirc) and these changes in xcode.

You can wait a day or two (or three ;-)) - we are rolling out 3.2 where this issue is fixed (and latest will be automatically selected)

3

Thank you so much for the quick reply. Unity does have an “Target iOS Version” = “4.2” option… but this doesn’t work either… I still get the stupid stuff described above. But anyway, I’m so glad to hear that 3.2 is imminent and this exasperating little niggle will be resolved.

Thanks again!

4

ouch, seems like i get the full scale of the problem. I will get back to you asap.

5

ok, i’m not so sure it’s gonna be fixed in 3.2 release (though i update here in any case)
Here is workaround:
find your Unity app → show package contents
go to Contents/PlaybackEngines/ Iook for iPhonePlayer or something - in here should be folder trampoline with xcode project. I can be wrong with some dir names but you need Unity-iPhone.xcodeproj
once again show package contents, open project.pbxproj
you need to search for “iphoneos3.2” and replace with
“iphoneos4.2” for 4.2
“iphoneos” for latest
(it should be only 2 occurrences)
Anyway, feel free to poke me here or by private message if in doubt about something :wink:

6

Should been fixed in 3.2

7

:smile: Cool. Thanks again Alexey. I hope I didn’t cause you grief with this question.

8

This is indeed resolved with 3.2. yay! :sunglasses: