Cannot build; libiPhone-lib.a

Unity Engine
,
1

Hi,

I am trying to get a Unity iOS export working in XCode, as I have to integrate a Unity scene with Vuforia plugin into an already existing iOS app. I set up a test project following this tutorial:
https://vimeo.com/136835530

But, I get the below error messages. I double-triple checked all paths ( Header search paths, Library Search paths) in XCode’s Build settings as well as the linked binaries and compile sources in the Build Phases Tab.
I try to run the app directly on a device (iPad mini, iPhone6), the Vuforia plugin will not run on the simulator.
I have been searching for a solution for hours, but to no avail.

Hope someone knows a hint. Thanks in advance.

XCode 7.1.1
Unity 5.1.3 fp
Vuforia plugin 5.0.6

PS: Just have seen that Vuforia 5.010 would support Unity 5.3, and that Unity 5.3.1 with a patch and fixes has recently been released. I will try this setup.

Undefined symbols for architecture armv7:
“RegisterStaticallyLinkedModulesGranular()”, referenced from:
RegisterStaticallyLinkedModules() in libiPhone-lib.a(RegisterStaticallyLinkedModules.o)
“RegisterAllStrippedInternalCalls()”, referenced from:
RegisterAllInternalCalls() in libiPhone-lib.a(MonoICallRegistration.o)
“RegisterAllClasses()”, referenced from:
InitializeEngineNoGraphics() in libiPhone-lib.a(SaveAndLoadHelper.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

2

I am running exactly the same problem, have you found any solution?

Thanks in advance

3

Hi Guys, i have the same problem.
You found any solution for this ?

4

Here’s an informed guess: I had somewhat similar build errors for a project that had been built with Symlink Unity Libraries enabled (in Build Settings) and then had the following done to it.

  1. Built and deployed to an iPhone successfully from XCode.

  2. The build directory was zipped into a .zip file and then unzipped.

Perhaps the symbolic links were somehow broken by that process. You might look into other ways that the symbolic links become unusable and see if they apply to your situation.