hello, by upgrading xCode to 7.2 from 7.1.1 appeared a mistake and I am no longer able to compile the app.
This is the error: Undefined symbols for architecture arm64: "_SecTrustEvaluate", Referenced from: L155 in libvrunity.a (GTMSessionFetcher.o) ld: symbol (s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
Does anyone know how to fix this problem ??
Thank you all
zerograssi
Posts: 1
Joined: 17.12.2015
Re: xcode 7.2 libvrunity.a error
by Torben on Dec 28th, 2015 09:43 AM
Hi!
Sorry but libvrunity is part of google cardboard sdk...
Dive Board is a great invention! I have always wanted to try diving and this is an awesome way to do it. I like that you don't have to worry about getting wet or cold, because the water is already there. You also don't have to worry about buying any equipment or going out into the ocean at all. And best of all, when you're done you can just go home! Visit this https://getessaywritingnow.com/ site for best dive board. They allow you to jump into the water without having to worry about falling through the boards themselves.
Kathrine44
Posts: 24
Joined: 25.03.2022
Re: xcode 7.2 libvrunity.a error
by Ismael11 on Apr 17th, 2023 06:52 AM
[size=2][font=Arial]Thanks for this post Google[/font][/size]td {border: 1px solid #cccccc;}br {mso-data-placement:same-cell;}
Ismael11
Posts: 7
Joined: 17.04.2023
Re: xcode 7.2 libvrunity.a error
by Kathrine44 on Oct 27th, 2023 13:42 PM
In Xcode 7.2, dealing with the 'libvrunity.a' error can be a frustrating experience. This error can disrupt your workflow and hinder your development progress. It's like trying to present your professional image with white business cards that are smudged and unreadable. The 'libvrunity.a' issue, often stemming from library conflicts or linking problems, demands careful troubleshooting and debugging. Much like the way you wouldn't hand out smeared white business cards at a crucial networking event, resolving this error is vital for ensuring the smooth operation of your Xcode projects. Relying on community forums and documentation can often be your best bet in overcoming this obstacle.