Log in or register to post comments

Vuforia Unity samples fail in Xcode 5.1.1

September 8, 2014 - 8:36am #1

latest Xcode, Vuforia, Unity, clean project directory, clean install Vuforia, testing one of the Vuforia samples this happens:

Xcode compiles App pushes onto phone and then it stalls on splash screen. In the Xcode Thread 1 /1 QCARUnityPlayer:getRotationFlag (char const*) [inlined]

then Thread 1: EXC_BAD_ACCESS(code 1 address 0x0)

any ideas? Is there some magick trick?

 

  • vuforia Unity extension latest version
  • Mac Os 10.9.4
  • Xcode 5.1.1
  • Unity version number 4.5.3p4
  • Device model iPhone 4s
  • iOS version 7.1.2
  • No Jailbreak or mods

Vuforia Unity samples fail in Xcode 5.1.1

September 20, 2014 - 2:08pm #6

You should be able to automate this by writing a PostProcessBuildPlayer that programmatically edits the Info.plist file;

see the Unity manual on the BuildPlayer pipeline:

http://docs.unity3d.com/Manual/BuildPlayerPipeline.html

 

Vuforia Unity samples fail in Xcode 5.1.1

September 20, 2014 - 11:20am #5

Hi, Thank you :) 

That solved the problem for me! Great.. But does that mean i have to do this everytime i run the build on my device ?

 

Thank you :)

Vuforia Unity samples fail in Xcode 5.1.1

September 19, 2014 - 12:40pm #4

See here for solution (note: the post mentions Unity 4.5.4, but it applies to your case as well, as the error is the same):

https://developer.vuforia.com/forum/unity-3-extension-technical-discussion/unity-454-and-vuforia-ios

 

 

Vuforia Unity samples fail in Xcode 5.1.1

September 19, 2014 - 4:17am #3

Hi, Where you able to fix this error without downgrading unity ?

I just created a new fresh project in Unity and installed vuforia 3.0.9 fresh as well.

Made a simple scene with a cube and exported to xcode.

But i get 8 Threads. With this errors: Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

Is there any solution other than downgrading the whole program in order to make it work.

 

Thank you :)

Fixed

September 8, 2014 - 11:17am #2

This car crash is fixed by using an older version of unity -  4.5.1f3 - because lets face it, youve got nothing better to do...

 

Log in or register to post comments