Hello,
I’ve had a failed attempt to get my game running on my iPad. The same game has successfully been complied as a PC and Mac standalone. So I made a very simple project to act as a test bed. It has one scene with a texture mapped onto an imported .fbx mesh from Modo. I’ve done my provisioning. My build settings are iPad only, Universal armv6 and armv7 (OpenGL ES1.1+2.0), native default device resolution).
Api Compatibility Level .NET2.0 Subset,
SDK: iOSlatest(since4.2)
Syripping Level Disabled
I’m using the latest version of Xcode which I downloaded 2 days ago. The original game plus the new minimal test project both compile and go to XCode. I hit run and get a successful compilation message. Both apps get as far as the Unity splash logo and hang. Going into the script I see where it says
UnityInitApplication(appPath) has a message Program received signal “SIGABRT”. In the linker warnings I get
Directory not found for option ‘L"/users/simesf/unity/projects/switch03/switch03001"’ plus a series of
ARM function mono ao…(variable messages) not 4 byte aligned.
I’m stumped. Anyone have any idea what’s going on? Any help much appreciated…
You can’t build for iOS SDK 4.3 and Base SDK 4.3, you need to use the 4.2 SDK at the time if you want to build anything with unity and send to the app store
Thanks for getting back to me. Is it the case that you have to uninstall Xcode 4 and iOS sdk 4.3, find an older version online of both online and install them to continue, or can you just specify within Unity to use 4.2 and Xcode will know to use the correct version of the SDK from those instructions.
The old SDK is no longer present. If you install 4.3, you only have the 4.3 SDK actually.
You will need to uninstall, download the 4.2 one from apple (the file is still there but not linked, different persons posted the link here and on google you will find it too) and install and use that one
Its an unhappy problem apple introduced with the release version of the 4.3 SDK, all beta versions didn’t have the messed up linker etc and worked fine
There’s the odd thing. I did a bit of searching and set the SDK deployment target to 3.2 and the app ran on my iPad. But I appreciate from reading posts here that I need the 4.2 SDK to submit to the app store. Thabks for the extra info.
Thats the problem that it won’t go to the app store. It likely might run on the local device but afterwards fails completely which gives a very dangerous security as there is nothing that prevents it from hiding other bugs behind it too which after a switch to 4.2 sdk for release for example popup out of the nowhere.