3.0 builds without issue, 3.1 (on latest Xcode) is a no go.
Error is:
ld: ldr 12-bit displacement out of range (4708 max +/-4096) in _AudioQueueAddPropertyListener$stub in _AudioQueueAddPropertyListener$stub from (build location info deleted)
Anyone seen this before?
HanulTech, what OS is on you mac? What OS is on your iDevice?
I was able to use latest SDK without any issues. Please see this topic for details.
I have 10.5.8 on my Mac. Machine specs:
Macbook Pro (2.93 GHz Dual Core 8GB Memory 1067 MHz DDR3)
I was building for a 3.1.1 iPod Touch device (just out of the box from Apple yesterday). I have the latest SDK and am using this version of Xcode 3.1:
Xcode IDE: 1203.0
Xcode Core: 1204.0
ToolSupport: 1186.0
I think I saw another update notice for Xcode so will try installing that to see if it fixes the problem. If not, I will submit a bug report and snapshot of the Unity project.
Also of note, the project builds fine for 2.2.1 and 3.0 devices.
Thanks
right, we’re aware of some bugs with latest iPhone OS version. Unity iPhone has been finished way earlier then OS 3.1, that’s why we tested it only with OS 3.0. Though we’re doing our best to release new version that’s aware of 3.1 OS.
I was just in the middle of updating my iPod touch from OS3.0 to 3.1.1 when i read this post and cancelled the update.
I am nearing completion of my iPhone app and don’t want to render my iPod dead for testing… so…
Can I still update the OS to 3.1.1 but build in xcode for 3.0 devices and run this on my 3.1.1 device (if that makes sense)?
I’ve also updated my iTunes to iTunes9…are all apps from now on required to be submitted to iTunes9 and does this in itself require OS3.1.1?
Sorry for semi-hijacking this thread, but my questions are related.
Regards,
Matt.
Yes, but if you update your development device to 3.1, then you need to update to the latest XCode (from my experience, the older one will complain it doesn’t recognize the OS on your device), and I’ve been able to get that to work with Unity still building for 3.0 devices (don’t even try 3.1), but it is flakier. If you’re almost done with your current app, I recommend releasing that before upgrading your setup.
2
Many thanks for this advice… i’ll stick with OS3.0 for the time being then.
Regarding my point 2… can i still submit apps etc using OS3.0 and does iTunes 9 has no baring on submitting apps etc and 3.0 vs 3.1.1?
Cheers,
Matt.
I don’t think I submitted any apps since the iTunes/iPhone update but since the app submission is performed via the iTunesConnect web page I don’t see how it would matter.
Apple is not requiring 3.1 only 3.0 and 1.5 builds against 3.0 without issue.
Unity:
I just submitted a bug report and project for an Editor GPF on another thread. That project is the same one that will not build on OS 3.1 if you want to look at that as well.
Thank you.
That’s interesting, I didn’t realize Apple is requiring 3.0 builds now. I started building with OS 3.0 anyway so I wouldn’t have to test with more than one OS (which is why I’ll probably build with OS 3.1 as soon as possible)
Based on the crash reports I have seen from them, Apple seems to test touch and phone apps on a 2G Touch running 3.0. If an app is phone only, I would guess they would test it with a 3G (not GS) running 3.0, but I have never submitted one.
I have not seen them test on anything other than 3.0, and they only require 3.0 compatibility. It will be interesting to see how soon they start testing on 3.1 and/or require it.
And I would add, that I have submitted two apps built with Unity 1.5 on OS 3.0 and they were accepted by Apple, so again there is no issue with 1.5 as it pertains to 3.0 or 2.2.1.
Well, eventually I was able to reproduce this bug. It’s Apple’s bug actually. New compiler/linker do something wrong. Unity can do nothing about this.
Of course I just recently updated my dev Touch to 3.1.1, so I have that going for me…
Is it possible to roll back to 3.0 safely? I have an app I’d like to get out this week, and giving it a test run or two would be nice. 
Also, what’s Apple’s recent approval time? Hoping it’s still around two weeks.
B.
Hey, what are the real issues, in using the latest SDK, having the DEV-touch updated to 3.1.1 and compile as 3.0 from XCODE, as it seems really the only 2.2.1 and 3.0 are working !??
In 15 days of Unity Iphone evaluation, we had no problems at all,
only the framerate difference among an Ipod Touch 8GB (3.1.1) and Iphone 3G(I believe it’s a 3.1.1 as well, not sure though, which I guess have the same graphic chipset and cpu) ,the ipod touch stays 30fps, the iphone sometimes laggs below, and reach 20fps.
Eheheheh, the more developers come in, the more will be the wait !
Great…
I am having this same problem as well. 
When I build from XCODE to 3.1 I get the same error message.
However, I can currently get around it by building to 3.0. So that is what I am doing for the moment.
Anyone know if I put a 3.0 build on the iTunes store if it will work for the latest iPhone operating systems for everyone else?
Not looking forward to a review lynching because the APP did not work for buyers.
Thanks.
I have been successfully building my Unity iPhone project against OS 3.1 for one week without issue. Yesterday, I went to build against OS 3.1 and received the linking error which is the subject of this thread.
ldr 12-bit displacement out range (5140 max +/- 4096) in _AudioQueueAddPropertyListener$stub in _AudioQueueAddPropertyListener$stub from (path to executable)
Does anyone know if there is a workaround for this yet other than building for OS 3.0? Problem is, I have custom classes added to the xCode project which enhance some functionality in the game and these classes contain code which rely on features in 3.1. I’m in a bit of a pickle here.
Cheers,
Nick
Yes, this is a known issue. If you look back in this thread, you will see this is the same problem I opened the thread with. Unity is aware of it, but I have not heard if there is yet a patch for it. I suggest you just build your app against 3.0 and submit it. 3.1 is not yet required by Apple.