We too are having this problem. We have tried everything we can think of.
Questions for Camx:
What version of xcode and what os are you running?
If anybody wants to discuss ping me @jfreeney on twitter.
My client had this exact error today too, and I had used AIR 18.104.22.1684. I've made a build with 22.214.171.1249 for them to try using, but I'm not expecting it to make a difference. Both of those versions of AIR are set to appear to have used Xcode 6.0, which should count as being later than 5.1.1.
Perhaps Apple had a mistake in Xcode 6.0, and do now require either 5.1.1 or 6.0.1.
I have emailed Adobe for comments on this.
Thanks for the info Colin. That confirms what we have tried also.
Don't forget that AIR doesn't involve using Xcode, it just has to appear to be the right version of Xcode. Only if you're using the Simulator does it then matter which Xcode you have installed. I mean, just think of Windows users, they can build iOS apps, and certainly don't have Xcode installed.
But as I said, yesterday's AIR update, and the one from the 18th, are both set to appear to be Xcode 6.0.0, and iOS 8.0.
I have tried the iOS 8 SDK and also tried the release of air version 15 and the latest beta version of 15.
I can't find anything on Google. An annoying bug because we need to push a new version of my app to fix some breaking changes in iOS 8.
They will fix this one quick Camx. Thank you Colin for the reminder that xcode does not matter
Thanks for reporting the issue. Could you please tell us how are you packaging the app, are you using Flash Pro/Flash Builder or command line? If was using Flash Pro or Builder, could you please tell us the packaging settings you used? Or Please share the exact ADT command used to package the application. Could you please share the xml/swf/assets with us?
Could you please try uploading a very simple HelloWorld application built with latest AIR 15 beta?
Adobe AIR Team
We are using Flash Builder with the most recent beta AIR SDK (289) using the default fast compiler. This is an update to an existing application and the build settings have not changed. I can not share the project but I will try to upload a simple test application in the morning (EST).
I'm using the export release build in flash builder 4.7 with the Air 15 build 289 sdk. You can find the ipa here if you want to have a look at it. http://www.tribalddb.co.nz/dev/flybuys/FlyBuys4.0.3.ipa
The build command used by flash builder is -
/usr/bin/java -d32 -jar /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_126.96.36.1999722/AIRSDK/lib/adt.jar -package -target ipa-app-store -hideAneLibSymbols no -provisioning-profile /Users/cameronc/Dev/AirApps/FlyBuys/fly0108-uat-my-fly-buys-3-1/certs/dis/Fly_Buys_App_St ore_2014.mobileprovision -storetype pkcs12 -keystore /Users/cameronc/Dev/AirApps/FlyBuys/fly0108-uat-my-fly-buys-3-1/certs/dis/LoyaltyNZDistri butionCertificates.p12 -storepass <Value cannot be displayed> MyFlyBuys.ipa MyFlyBuys-app.xml assets Defaultemail@example.com Default-Portrait.png Default-Portrait@2x.png Default.png Default@2x.png Icon114.png Icon120.png Icon128.png Icon144.png Icon152.png Icon29.png Icon36.png Icon48.png Icon512.png Icon57.png Icon72.png Icon76.png MyFlyBuys.swf -extdir /Users/cameronc/Documents/Adobe Flash Builder 4.7/.metadata/.plugins/com.adobe.flexbuilder.project.ui/ANEFiles/MyFlyBuys/com.adobe.flex ide.multiplatform.ios.platform -platformsdk /Developer/Platforms/iPhoneOS8.sdk
Thank you for your reply, we're able to reproduce the problem. Looks like, something has changed from Apple side recently, we're investigating.
Hi all, I'm getting this issue as well this morning when submitted a new build of an app that I successfully submitted yesterday. When I revert the new change I still get the same error.
Look forward to hearing any news of a fix.
Just to confirm that I am also having this problem. Using the latest Flex SDK 13.0.1 with Air 15. I uploaded an app just two days ago, on the 23thd, and everything was fine. I wanted to upload a new build today and the "Invalid Segment Alignment" error showed up.
I just got the same problem.
Yesterday it was working fine.
But I got this problem after regenerating the certificate and provisioning profile. I did that because apple has introduced new "TestFlight" system for beta testing. And as a solution they are asking developers to regenerate the certificate and provisioning profile to include "TestFlight" entitlement in the package.
After using the new certificate with new profile, I got this error.
I am also waiting for the solution to this problem as soon as possible.
1 person found this helpful
It seems there have been changes in way Apple expects the apps to created. We investigated this deeper, and found that the output of our linker (in our toolchain) is no longer being accepted by Apple.
We are working on this to upgrade our toolchain, including the linker. For the time being, we would suggest you to try using the ‘linker’ available on the system. We have done tests with a couple of apps and it seems to be fixing the problem. Please give it a try and see if it can unblock you. Please note that this workaround is applicable only for Mac platform.
Steps to make use of system linker -
mv ld64 ld64_orig
ln –s /usr/bin/ld ld64
<Build the IPA now using Flash Pro, Flash Builder or on command line>
Before the submission, we recommend to test the application functionality as well. Please keep us posted with more information in this regard. It will help us fix our toolchain sooner and in a better way.
I m having the same issue , and i m using Flash Professional CC and the latest SDK , i'm using an ANE everything is working perfectly in My device and any other device also on IOS Simulator . and today i got that error when i submited my IPA .
We have a serious problem and the client is waiting for long time the app to be on the Store
I have the problem to. But how to do this in flash CC?
The same problem has also occurred me.
Withdrawal your own app, I was up again.
Could it be that might be the difference in the display version and build version.
I feel like can only Xcode to this(build version).
I have changed the info.plist in Xcode5 of MAC.
Then, sign and was up in ApplicationLoader but it's the same.
Hi i have executed to system liker , exactly how it is written after i exported my app using Flash CC ( i ve used the same sdk in system linker ) , but i showed an error i think is simple :
SDK is missing file /Applications/Adobe Flash CC/AIR3.6/lib/aot/bin/ld64/ld64
I think it is because i moved the ld64 to ld64_orig and the creation of the syslink was not perfect , i ve checked in the folder "<sdk>/lib/aot/bin/ld64" the ld64 is there as a link .
but the problem is that the ld doest not exist in "/usr/bin/" .
so what can i do i think is simple ?/
Pahup, Thanks for your answers. It solved the problem. But could you please suggest why we are getting the following warning on the prerelease screen in itunes connect:
"To use TestFlight Beta Testing, this build must contain the correct beta entitlement.
Faq on apple regarding this:
What should I do if my prerelease build does not contain the correct beta entitlement?
You need to sign the app with a Distribution Provisioning profile that contains the beta entitlement. Distribution Provisioning profiles can be generated in the iOS Developer Center.
If you have an existing Distribution Provisioning Profile that was generated before the launch of TestFlight Beta Testing, you may need to regenerate the profile. "
I regenerated the certificate and provisioning profile, but still I am getting the same warning. Can we avoid this warning? or Builds with this warning will be rejected by apple?
Thanks in advance.
Changing the linker as suggested allowed us to submit a new build for an app that had been rejected early this morning.
We've exhaustively tested the app on the following devices:
- iPad 1
- iPad mini
- iPad mini retina
- iPad 3
- iPod 4th Gen
- iPod 5th Gen
- iPhone 6
- iPhone 6+
No issues detected.
I've done the System linker successfully , i got the ld file from Xcode bin and i've packaged my app successfully everything is working perfectly . i submitted to the Apple Store i got the same Error . .. ( the new "ld" is the "ld" on the Xcode Version 4.6.3 (4H1503) that i'm using now for my ANE's )
Are using the latest Xcode ( the "ld" command) ?
I have Xcode v6.0 (6A313) installed.
I can confirm that using the Mac linker fixes the upload error in iTunes (Application Loader), great!
I have not tested the compiled ipa yet. I will do that in a couple of hours and report back.
Thanks for posting this fix so quick! As I am developing on Windows, I hope a fix for Windows will be possible soon.
Xcode is at 6.0.1 now, not sure what build number that is.
I'm having the same problem, I'm using Flash CC 2014, AIR 188.8.131.529 and Application Loader version 3.0 (620) - X-code version 6.0.1 (6A317).
Please can you give more details about the workaround? I dont know how to modify the linker, or even where to look.
Trying these steps gave me a no such file or directory error. So instead I left the renamed file there and copied the Apple ln file and renamed that to ln64. That almost worked, but I got an error about the Xcode path. That happened because I was using Xcode 6 a while ago as “Xcode GM”, and had gone back to it being called “Xcode” when the release version came out. Seems that Flash was still remembering my renamed version.
That was fixed with this line:
sudo xcode-select --switch /Applications/Xcode.app
Then the app built ok. This is from within Flash Pro, I didn’t use the command line for the build.
Will get my client to try resubmitting this version.
We're seeing this now too.
The really annoying thing is that we submitted the app 3 days ago, got accepted for an expedited review and then during the review they updated their requirements and rejected the binary!
Now we can't even upload a binary due to this error.
Last week we had an app accepted using the exact same Air SDK etc....
This is SO frustrating...as you can imagine even more so with a client being told they have an expedited review and then this with no clue how to fix it.
Hmmmmm will keep an eye here but I suspect we need a new release of Air SDK?
Steve, I'll know later if my approach worked ok. If it did then it would be possible to do the work around just in the Finder, without involving Terminal.
Whether you do this in Terminal, or Finder, you'll need to track down where the files are located. If you downloaded the AIR SDK and left it in your Downloads folder, the original ld64 file will be here:
So, in the command line instruction above your first line would be:
Assuming you are "steve" as a user name!
Dave, read all of this thread, especially Pahup's work around, and my additional notes.
Thanks Colin...sorry, not sure how I missed that specific reply! Thank you all.
Thank you for your reply Colin, I'll give that a go
I'm having the same problem. Any estimate on a timeframe of when it will be resolved?
Hi @ljb2411 - Pahup has posted a workaround above (for OSX users, using the
system linker), and said they're working on the toolchain fix.
Thanks, Pahup and team!
My app is in the queue (submitted last Thursday before this became a
requirement), so I'm likely to be rejected. I'll post back with an update.
BTW guys, I had fun finding the Xcode ld file...for me it's in this location:
I expect that one will work, but I used the one that Pahup pointed to. You can get to it in the Finder by choosing Go/Go to Folder... and typing in:
Can anyone explain in simple language how to fix this then? I use Flash CC and the latest AIR15 beta on Windows
My client's app successfully uploaded with the work around. I'm waiting to here if it's now in the review queue, but there's hope.
For Windows users it might just be that taking the Apple linker and replacing the Adobe one will work, but I'm not sure if that file is code, or just data. Also it may not be legal to give people bits of Apple code, no matter how small it is.
Are you at the stage of needing to submit an app?
yes i am