App crashes as soon as splash screen is displayed(even just camera).

As mentioned above the app is crashing as soon as the splash screen is displayed. Its a new Mac,OS Maverick, Latest Xcode and Unity 4.5.5 if anyone needed the specs. The xcode is also not creating the dsym file at the end as it used to do in the previous versions. Please help !!

 

Hi Mantas,
Thanks for the reply. The same app is working fine on xcode version 5 and Unity 4.3.2.I checked the xcode debugger console and I got this message
{
2014-10-30 13:15:44.683 app_name[2702:543400] -> registered mono modules 0x1b3ee80

-> applicationDidFinishLaunching()

Mono path[0] = '/private/var/mobile/Containers/Bundle/Application/9CE54280-D811-40B1-A250-5FB66011B2EC/app_name.app/Data/Managed'

Mono config path = '/private/var/mobile/Containers/Bundle/Application/9CE54280-D811-40B1-A250-5FB66011B2EC/app_name.app/Data/Managed'

-> applicationDidBecomeActive()

(lldb)
}

And the stack of main thread is {
#import <UIKit/UIKit.h>


#include <time.h>

#include "RegisterClasses.h"

#include "RegisterMonoModules.h"


// Hack to work around iOS SDK 4.3 linker problem

// we need at least one __TEXT, __const section entry in main application .o files

// to get this section emitted at right time and so avoid LC_ENCRYPTION_INFO size miscalculation

staticconstint constsection = 0;


void UnityInitTrampoline();


// WARNING: this MUST be c decl (NSString ctor will be called after +load, so we cant really change its value)

constchar* AppControllerClassName = "UnityAppController";



int main(int argc, char* argv[])

{

NSAutoreleasePool* pool = [NSAutoreleasePoolnew];


UnityInitTrampoline();

if(!UnityParseCommandLine(argc, argv))

return -1;


RegisterMonoModules();

NSLog(@"-> registered mono modules %p\n", &constsection);


UIApplicationMain(argc, argv, nil, [NSStringstringWithUTF8String:AppControllerClassName]);


[pool release];

return0;

}



#if TARGET_IPHONE_SIMULATOR

extern"C" clock_t clock$UNIX2003(void) { return clock(); }

#endif // TARGET_IPHONE_SIMULATOR
}

 

Here is a screenshot of the same

 

you're using wrong / not compatible / old version of vuforia

 

Yes I actually resolved the error just some time back. I'm sorry I didn't get time to reply. It is indeed a problem with vuforia. I added an extra key String in the device Orientation and the issue got resolved. Thanks for the help everyone.