“Your binary is not optimized for iPhone 5” after I upload an app with xcode 6.0.1

Question

I am getting this email after upload my binary with Xcode Version 6.0.1 (6A317)

Your binary is not optimized for iPhone 5 - - New iPhone apps and app

Answer 1

Do what Charlie and Dan recommend AND make sure that your image file names don't have any dashes in it. Mine didn't work until I renamed the files as only alphanumeric.

Answer 2

I got the same error in deployment environment 9.3 and swift 2.3 and in my case I didn't had the storyboard (xib) file for the launch image, which is needed and my configuration was wrong in projects target settings, see the image link below:

Picture of Settings

Answer 3

Maybe this is useful for some guys: just change the iOS Deployment Target from 7.0 to 8.1 or higher.

I met this problem when I want to upload an app to app store built by react-native 0.37, and its default iOS Deployment Target is 7.0.

Answer 4

In my case, I was updating an older app. It turned out I was missing an icon file named: launchiPhone5-568h@2x.png with dimensions 320x568. I found this by looking through the warnings. I created the file, added it to my project with the other icon files and it worked fine.

Hope that helps someone :-)

Answer 5

We faced the same issue and couldn't solve it after trying many solutions, we believe it's a kind of bug in App submission. But we found a workaround which can keep launch images localized and pass the submission verification.

Environment:

Xcode 6.1 (6A1052c) with iOS 8.1 SDK

Precondition:

Have following properties in your "*-info.plist" file.

Steps:

1. Go to your target's settings and in our standard scenario (localize launch images, which uses "UILaunchImages" in "*-info.plist" but not image assets), it should look like the image

2. Change the setting to use image assets (Note: after this step, Xcode will automatically REMOVE the "UILaunchImages" properties in your *-info.plist file. So please BACKUP the properties first.)

3. Go to the "LaunchImage" assets (can click the arrow button on the right) and fill with images from one of your *.lproj folder.

4. Now, go to the "LaunchImage" folder which contains images and "Contents.json" file.

5. Remove ALL the launch IMAGES just added, but keep the "Contents.json" (and it's content) file.

6. Check the "Contents.json", it should contains properties like image below

Double check following items:

• Localized launch images in resource folders (en.lproj, ja.lproj, etc.)

• *-info.plist contains "UILaunchImages" properties

• Project setting uses image asset for launch images

• "Contents.json" in "LaunchImage" asset folder, and the folder DOES NOT really have launch images

Now you can have a try for localized launch images and submit the binary to iTunes Connect. In our App, the workaround did work for "localized launch images" and "submission successful".

It should be a trick for avoiding the bug in submission checking.

Since the workaround above doesn't change any resource, except making the checking thinks we use image assets, we are more convinced that there are some bugs in Apple's checking.

Cheers!

Answer 6

This happened to me too. Since iOS6 (I think) if you localize your app you must be consistent all the way. You have English, Dutch, and French as languages as I see in the screen shot. You must have these languages EVERYWHERE you do localization. Your string localization files must have all these languages but not more languages. I got the same reply when I used AppiRater library for an app. AppiRater has messages in many languages and my app is localized only for 2 languages. So I had to delete all the other string files from AppiRater except the 2 that I needed. Once I did that everything went well.

So the short answer is: delete any extra localization files that you don't need to support and add localization files that are missing from your app.

Cheers!

Edit by danielgindi

This actually works, despite some claims that this answer is irrelevant. It happened to me when I started using Base localization in an app, and it still had some resources localized in en.lproj folder, including the Default.pngs.

So you can either make sure that you have the Default-568h@2x.png file in all of the localization folders that you are using - or delete localizations that you are not using. I have just moved everything to be in Base.lproj, so this way it's clear what png it is taking, and there's no duplicate.