iPhone 3.1 build error

Crazy_Robot · July 1, 2009, 2:48am

I upgraded my phone to 3.1 beta and my app gets an error now:

ld: ldr 12-bit displacement out of range (4544 max +/-4096) in _AudioQueueAddPropertyListener$stub in _AudioQueueAddPropertyListener$stub from /Users/…
collect2: ld returned 1 exit status

When I build it under 3.0 with XCode 3.1 is builds fine.

I know 3.1 is a beta, but I just wanted to let everyone know there seems to be an issue with Xcode 3.1.

cheezorg · July 1, 2009, 5:48pm

Thanks for the heads up.

anon_28206345 · July 31, 2009, 2:58pm

I’m getting this error as well, any idea what might be causing it?

Mantas-Puida · August 2, 2009, 7:26pm

Hello,
please submit bug report to Apple. This will help them fix beta issues.

Jessy · August 25, 2009, 5:14pm

Unity iPhone 1.5 did not fix this problem. I am only able to build for anything prior to 3.1.

Crazy_Robot · August 25, 2009, 6:09pm

Yeah,

It’s not a Unity issue, it’s an Apple issue.

anon_19413382 · August 26, 2009, 6:26am

Eric5h5 · August 26, 2009, 7:00am

I think you’re a spammer and should be deleted.

–Eric

Crazy_Robot · August 26, 2009, 2:01pm

Has anyone else submitted a bug report to Apple?

anon_28206345 · August 31, 2009, 11:10pm

I also reported the bug to apple, but haven’t heard anything back from them yet. Only one other person has reported seeing this on their forums…

I’ve been doing some 3.1 development outside of Unity and haven’t run into this issue. It seems to be related to the amount of code: the project reaches a certain threshold at which point any inane line of code will push it over the edge. Also, if you’re using the new native plugin support it happens much sooner (requires less extra code to cause it). I’m sure all this has to do with the general footprint of the application - Unity projects are a good bit larger than native ones, so regular iPhone devs might not be seeing this.

Just FYI, I’m using all C# scripts (no javascript).

Hoping for a fix soon! (be it from Apple or Unity) This is a bit of a show stopper for our projects at the moment…

anon_76695274 · September 13, 2009, 3:06pm

Having this problem at the moment. Anyone find a fix?

Dreamora · September 13, 2009, 3:20pm

with the released 3.1 and released 3.1 SDK that problem does not exist, at least not for me.
Ensure you kick out bliprobs enhancement kit when testing

Lostlogic · September 13, 2009, 3:55pm

Can you share your settings?

I just did a build and run on the iPhone Match Example and now get the Ldr 12-bit error. Right now I have Device - 3.1 selected as the test device.

Dreamora · September 13, 2009, 4:06pm

Default settings, no changes to them. Project as generated by UT without any modification or build script that alter it, only change beeing the revisions

Lostlogic · September 13, 2009, 4:12pm

It seems selecting Device - 3.0 fixes the problem for now.

anon_76695274 · September 13, 2009, 4:16pm

Great, thanks! Selecting 3.0 also works for me.

gametr4x · September 16, 2009, 4:08pm

I’m getting this problem as well. Building for base sdk 3.0 and Release 3.0 works, but I can’t upload it to my device since it is 3.1 now

I hope somebody finds a fix for this asap.

Jessy · September 16, 2009, 4:13pm

OS 3.1 runs content created for earlier versions. I don’t see how this would cause a problem for you.

gametr4x · September 16, 2009, 4:20pm

My xcode does not recognize that my iPod Touch is connected when I build Release 3.0. It just says “No Provisioned Devices Connected”. Do I have to create a specific provisioning profile for the 3.1 device?

EDIT: I had to re-add the device in my organizer after the update. Silly me…

Wozik · September 18, 2009, 2:39pm

Blame Apple coders and submit Apple bugreport. Its their compiler-linker error. Unity can do nothing about it.

Until they fix this case you may compile for 3.0
it seems to work OK