Building my Unity 3 iPhone/iPad App on XCode 4.0.2 blog - Gamieon

Now that I'm using XCode 4.0.2 and Unity 3.30f4, I see that a lot of things have changed since my XCode 3.x and Unity 2.x excursion. Some things I noticed right away:

- No more one-click build-and-debug sessions. I now have to do Build & Run from Unity, and then press the Run button in XCode 4.

- It takes less steps to build an app for ad-hoc deployment. Most of the settings are what they should be off-the-bat.

So now it's time to start giving out ad-hoc builds of Hyperspace Pinball. Here is the list of things I now do in XCode after I click "Build & Run" from Unity:

1. In the Classes node in the tree on the left, go into appcontroller.mm and ensure USE_OPENGLES20_IF_AVAILABLE is set to 0.

2. Left-click on "Unity - iPhone" on the top left of XCode

3. In a pane just to the right of where you clicked there should be a "Targets" section with "Unity - iPhone" and "Unity - iPhone-simulator". Left-click on "Unity - iPhone"

4. In the Summary tab- Ensure the first four parameters are correct. My identifier is "com.gamieon.{the name of my game all lower-case and without spaces}"- Under supported device orientation, uncheck everything but Portrait.

5. In the Info tab- Rename the Bundle display name to "Hyper.Pinball". I have to do this, otherwise it looks like "Hypers...nball" in the iPhone menu.

6. In the Build Settings tab- On the top left is a toggle for "Basic" and "All". Ensure "All" is selected.- Architectures: armv6.- Build Active Architecture Only: No- Valid Architectures: armv6 armv7- Code Signing Identity: Hyperspace Pinball Ad Hoc- Everything under Code signing identity should also be Hyperspace Pinbal Ad Hoc.- iOS Deployment Target: 3.0

(all but the provisioning profile were all set for me, but just double check)

7. In the Build Phases tab, add GameKit.framework if it's not already listed.

8. Press Command-B to build.

..and that should be it. I'm foregoing forcing MinimumOSVersion in info.plist with the value 4.0 for the moment. I want to see how testing pans out.