Just got through updating to Snow Leopard… and updated XCode to v3.2… launched a Unity XCode project and it wasn’t recognizing anything iPhone related.
I then realized my iPhone SDK needed to be downloaded for Snow Leopard… downloaded it/installed it. Opened up the Unity XCode project again and most of the frameworks in the Groups Files sidebar were red… but if I built the project it didn’t have any errors. This still bothered me.
It would seem the base SDK was for iPhone OS 2 was removed after the new XCode was installed… no big deal for me, but it caught me by surprise…
After I opened the Unity XCode project template I right-clicked on the blue project icon in the Groups Files sidebar and got info on the project. Under the ‘Build’ tab, change the Base SDK value to iPhone Device 3.0… and all should be back to normal as far as I can tell.
Anyone else have anything to add to this? Am I missing anything?
I’ve just done this too. Installed Snow Leopard and Xcode 3.2.
I followed your advice, namely installing the Snow Leopard version of the iPhone SDK. Missing SDK2 target as you said.
I edited the trampoline project and rebuilt everything. I also had to go change the target device in my game xcode project. Not sure why, because I expected it to be overwritten by the trampoline.
Anyhow, all is good now - no problem building and deploying my app.
Oh man, I totally forgot to put that in… I guess I just got used to switching that popup list all the time if I don’t have my iPhone plugged in when I open the xcode project!
Shortly after install, I noticed that each time I edited something in Unitron and switched back to Unity it would completely go through and reimport my assets each time… like I was opening/exporting the project…
You see anything like the assets reimporting?
But now I don’t see this at all… I’m not sure, though I do suspect everything worked better with Snow Leopard after I did a full shut down vs. the installation CD’s soft restart after install…
Actually, I can’t be sure whether this was after the iPhone 1.5 upgrade or Snow Leopard upgrade, but when unity lauches Xcode, it no longer automatically builds, it just installs and runs the app.
I have to manually click build and run in xcode, and xcode has also become non responsive on occasion after ending the debug session.
Hmm… I haven’t ran into the build issue out of Unity. I do however export my xcode project since the build-n-go to XCode would get out of whack if I didn’t have an iPhone plugged in or it was plugged in and it was loading… ran into too many issues so I just took a manual approach and just built it each time.
I am now also getting this behavior… Definitely new behavior since my upgrade to Snow Leopard yesterday. Not sure if this is an XCode problem or 1.5 problem…
Remember that Unity no longer overwrites your XCode project each time you do a build and run, so it’s possible XCode doesn’t know that anything has changed. In this instance it will simply install and run the project without building.
Hi Peter - good idea, but I never experienced this while testing the 1.5 beta - and I use the new “append” feature to access native Obj-C stuff… Definitely feels like a Snow Leopard thing at the moment. Or more likely bugs in the new XCode, since I hadn’t upgraded that either Thanks!
Ok. So this would make sense according to our friend Perter D. If unity no longer overwrites the project, Xcode would have no reason to build. One click deployment would be improved then if unity touched th project as part of the “build” and run action.
Otherwise, it’s your own build an run process that need to be implemented. I guess I’m bit lazy.
Thanks!