Out of the blue my iPad project is terminating on launch. It was working this morning, and I haven't changed anything ? -> applicationDidFinishLaunching() Failed to load AOT module '/var/mobile/Applications/F18A0925-58EF-4833-A569-7DF1E98BF63C/touchfootball.app/Data/Boo.Lang.dll.dylib' in aot-only mode. I was seeing this error with first pass.dll.dylib but after cutting down the project to the bare minimum of assets this is what's left. Grrr. I'm not even using boo! Filing a bug next.
if you have a single js file in your project your are actually using boo / parts of it as JS relies on boo.
Thanks. I'm using the dual-joystick js. Deleting that, removing the file from the bundle, trashing the iPhone OS project -- still getting this error. I've restarted the device and will reboot my dev system once the 4.0 SDK finishes DLing.
Did you reinstall the OS on your iPad or reinstall the SDK? I'm getting this same error and can't seem to shake it. Reinstalled the OS 4 SDK but no luck.
I just ran into something similar, but with CSharp.dll, after successfully releasing several other iPhone+iPad projects. Code (csharp): 2010-04-25 20:40:48.812 FuguType[4097:207] -> registered unity classes 2010-04-25 20:40:48.823 FuguType[4097:207] -> registered mono modules -> applicationDidFinishLaunching() Failed to load AOT module '/var/mobile/Applications/BFAE1830-C7A2-4857-A11D-2470F67BB965/FuguType.app/Data/Assembly - CSharp.dll.dylib' in aot-only mode.
I really don't know if my reinstalling the OS on the device was necessary. I guess the first thing to do is quit everything and toss/put aside the existing xcode project and let unity rebuild it from scratch. I've been running the OS 4 SDK with no problems now.
I had this (the Boo version) and deleting the existing install of my App on my device fixed it. Next time I built the project and it installed to the device, it worked. Go figure....
I had a related problem. The solution describred at http://forum.unity3d.com/viewtopic.php?p=379674 also solve this problem (Love this forum!!!!!)
Will this cause users in the app store who upgrade the app to experience a crash until they re-install?
I have only seen this issue when building to device via Xcode. e.g. no issues with TestFlight distribution.