Unable to build project using latest unity and latest xcode.

I have banged my head against this for a good day now, and I am unable to resolve this - We have Unity Pro and Unity iOS Pro, but using the latest XCode I am not able to build a project that uses a native plugin to an iOS device. The plugin in question we're using is the "Powered by String" AR library, this has worked before - but after upgrading everything to the latest version, I can't get this error to go away:

Code (csharp):

1.  
2. Undefined symbols for architecture armv7:
3.   "HandleOrientationRequest()", referenced from:
4.       _String_SetProjectionAndViewport in libStringUnityDemo-1.1.3.a(StringAppController.o)
5.   "ShouldHandleRotation(ScreenOrientation*)", referenced from:
6.       _String_SetProjectionAndViewport in libStringUnityDemo-1.1.3.a(StringAppController.o)
7.   "UnitySetAllowOrientationDetection(bool)", referenced from:
8.       _String_LoadImageMarker in libStringUnityDemo-1.1.3.a(StringAppController.o)
9.  

 

I am having the exact same problem as you are, I just cannot seem to get past these errors. It is no help at all that this is my first time trying to get the app to build. I am trying to do a HelloWorld with the String Augmented Reality tools and this happens to be my latest issue. Any help would be greatly appreciated.

Code (csharp):

1. Undefined symbols for architecture armv7:
2.   "HandleOrientationRequest()", referenced from:
3.       _String_SetProjectionAndViewport in libStringUnityDemo-1.1.3.a(StringAppController.o)
4.   "ShouldHandleRotation(ScreenOrientation*)", referenced from:
5.       _String_SetProjectionAndViewport in libStringUnityDemo-1.1.3.a(StringAppController.o)
6.   "UnitySetAllowOrientationDetection(bool)", referenced from:
7.       _String_LoadImageMarker in libStringUnityDemo-1.1.3.a(StringAppController.o)
8. ld: symbol(s) not found for architecture armv7
9. clang: error: linker command failed with exit code 1 (use -v to see invocation)

 

I am also having the same problem. Did any of you find what was wrong yet? Or how to fix it?

 

I'm getting the same issue. Anyone worked it out yet?

 

Since Xcode 4.5, you have to add custom frameworks manually (xcode > target-iPhone > build phases > link to libraries).
It was done automatically before.

 

Has anyone resolved this issue?
The basic tutorial does mention including the appropriate frameworks so I don't think that's the issue.

 

Just asked about it from String themselves (am I the only one who bothered?) and they replied they're working on to support newer Unity versions. They say 3.5.4 should work for now, if you're able to get your hands on that.

 

I am using Unity 3.5.6f4 and xCode 4.5.1 and i get following errors in xcode when try to build:

PHP:

Undefined symbols for architecture armv7:
  "HandleOrientationRequest()", referenced from:
      _String_SetProjectionAndViewport in libStringUnityDeveloper-1.1.3.a(StringAppController.o)
  "ShouldHandleRotation(ScreenOrientation*)", referenced from:
      _String_SetProjectionAndViewport in libStringUnityDeveloper-1.1.3.a(StringAppController.o)
  "UnitySetAllowOrientationDetection(bool)", referenced from:
      _String_LoadImageMarker in libStringUnityDeveloper-1.1.3.a(StringAppController.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Any solutions for that? Thanks

 

Read the thread? Like the last post before yours.

 

Resurrecting this thread, seems String hasn't updated their stuff at all (in fact, seems nothing about their support really matches their attempt at premium pricing).

Also, installing Unity 3.5.4 (shameful as it is that any developer would suggest doing this) doesn't fix the problem

As it is, String appears "dead in the water" which is too bad, because the tech looked like a good performer.

 

String project is dead. Don't use it.

 

What you mean String project is dead?

 

Yah, we decided on Qualcomm's QCar (which actually isn't a car! haha).

It's not the most Unity friendly workflow but easy to pick up, works great, good performance, and the developer doesn't try to gouge other devs with ridiculous license schemes (!)

Does everything we need