Skip to main content
cybobear
cybobear
Inspiring
February 10, 2018
Answered

Your binary is not optimized for iPhone 5 (ITMS-90096) error when submitting to apple

  • February 10, 2018
  • 1 reply
  • 3575 views

I'm getting this error out of the blue when trying to update my app. I have spent a lot of time including every dimension with proper naming conventions of the launch image with no luck. I looked through this post: Re: “Your binary is not optimized for iPhone 5” (ITMS-90096) when submitting

And confirmed that the images are indeed in the package. I'm using Animate to package the ipa for distribution to the app store. Can anyone shed some light on this?

Thanks,

-Cybo

P.S. I have to add that the cumulative time I've spent troubleshooting Application loader errors when deploying to iOS is so frustrating! I never have issues to this degree with Android.

This topic has been closed for replies.
Correct answer el111

So this did pass the app loader gate, but then got rejected with this error from itunes connect:

Missing Asset Catalog - Your app is missing the asset catalog file

I'm working on it now referencing this thread: Error message when submitting an app to the AppStore


re: Missing Asset Catalog

This is the Assets.car you need to include.

If you have already created it by following the Adobe release notes instructions then you may have forgotten to also package it.

1) Place file in root of your project - where you have your Main.as

2) in your app.xml

<!-- iOS specific capabilities -->

    <iPhone>

        <assetsCar>Assets.car</assetsCar>

    </iPhone>

3) Then, you also need to add it as you did with your splash screens via the + button.

re: splash and individual files.

You can package a folder's contents using adt by using "." at the end eg

/my/splash/folder/.

I don't use Animate but would have assumed you could use ctrl or shift to select multiple files. If not that is a pain!

1 reply

cybobear
cybobearAuthor
Inspiring
February 10, 2018

OK, I've narrowed it down to a bug in AIR. I targeted AIR 27 and the binary was accepted by Apple. So this must be an issue with the packaging code around the launch images in the AIR 28 SDK for iOS. Argh this cost me 5+ hours. Now I know to try that troubleshooting step sooner.

cybobear
cybobearAuthor
Inspiring
February 10, 2018

I added this to the adobe bug tracker.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices