Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnityGfxDeviceWorker (18): EXC_BAD_ACCESS (code=1, address=0x1) (Unity 2017.3.0f3 & Vuforia 7.0.36) #34

Closed
ohwhen opened this issue Jan 8, 2018 · 3 comments

Comments

@ohwhen
Copy link

ohwhen commented Jan 8, 2018

I realize this project is strictly for Unity & iOS integration but I'm running into the same issues as #4 I made sure I included the right NSCameraUsageDescription in the plist file and tried following the advice in this reply but to no avail.

Everything works flawlessly when I run the demo app. But as soon as I drag a Vuforia ARCamera object into the Unity project and try to build I'm running into this error. This even happens with the DemoApp (drag ARCamera object onto scene and rebuild)

Stack trace

0x102d42414 <+40>:  bl     0x103f71f60               ; symbol stub for: objc_retain
0x102d42418 <+44>:  mov    x19, x0 UnityGfxDeviceWorker (14): EXC_BAD_ACCESS (code=1, address=0x1)

Console

System.Array:Resize(T[]&, Int32, Int32)
Vuforia.ITrackerManager:GetTracker()
Vuforia.ITrackerManager:GetTracker()
Vuforia.ITrackerManager:GetTracker()
 
**Debug Navigator**
(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

(lldb)

screen shot 2018-01-08 at 4 05 53 pm

@JasonPan
Copy link

I had this issue and found that it was because Metal was enabled in my Unity project.

Try going into your Player settings -> Other Settings and

  • turn off Auto Graphics API,
  • delete 'Metal' from the Graphics API list.

Hope this helps!

@jiulongw
Copy link
Owner

jiulongw commented Feb 2, 2018

Thanks @JasonPan .

@ohwhen , feel free to re-open this issue if you still have problems.

@jiulongw jiulongw closed this as completed Feb 2, 2018
@ohwhen
Copy link
Author

ohwhen commented Feb 2, 2018

Thanks @JasonPan we already found the exact same solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants