iPhone Match Game Example - Build Error

I’ve looked at the iPhone Example for a simple match game (it’s labeled as a iPhone example at least) but when I go to build and run it on my device it gives a build error:

Ldr 12-bit desplacement out of range (5700 max +/-4096) in _AudioQueueAddPropertyListenserStub.............

Command/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 failed with exit code 1

One thing I’ve noticed in the ray picking script is that it is using the mouse for input. Should it not be using the touchscreen? I could be wrong on this since the linker appears to be choking on the audio.

I pulled the sample project from this page: Unity - Manual: Getting started with iOS

Any ideas what I’m doing wrong here? My project is not saved in the Assets folder by the way.

Thanks,
GO

Sorry, didn’t see the other thread about this being a 3.1 problem with XCode. Please ignore, although you can feel free to bug apple about the code gen error. :slight_smile:

I’ve the same problem, how did you fix it?
Thanks

Yepp, yet again Apple has brought some nice surprises for all.
But we’re aware of this issue and trying to solve it. Thanks for your time and patience.

Just to be sure. I’ve installed brand new full package of iPhone SDK 3.1 downloaded from Apple website to a fresh virtual machine. Downloaded that match game demo from our website and guess what? Everything does work OK with Unity iPhone 1.5 build 26882. Tested on iPod touch 2 with OS 3.0

I’ve tried compiling with bundled SDK 2.0 and SDK 3.0 and haven’t seen any errors or issues. What might I have done wrong? :wink:

I am just curious what the status of this issue is. I have been having various issues since 3.0 came out. The primary issue I experience is when clicking “Build and Run” it will build Xcode and compile/deply to my phone just fine. When I stop Xcode and click “Build and Run” again it always errors.

I recently integrated OpenFeint into a project and am getting the following error:

Currently one can experience issues only when compiling for 3.1 or 3.1.2. Otherwise it should be OK both for OS 10.5 and 10.6.