I get the following message once the binary is uploaded.
Your binary has been received but does not meet all the requirements for submission
What things could be wrong? It works fine on a device.
You need to make sure that your binary has the required artwork, icons and is signed properly. You should suit using the application loader. Using Xcode will work but won't tell you what your issue is.
You may have:
Signed with a development certificate instead of a distribution certificate
Not included the 512px square iTunes artwork
Not included default launch images
Not included icons
A space in your binary name. This may happen if your project name has a space in it. Just rename it in Finder.
I referred to the below link and followed the steps as mentioned by Riceo
What can cause "invalid binary" with no email followup from iTunes Connect?
It gave me following Error while validating in Organizer as my appname needed to contain whitespace
My app.ipa filename may not contain whitespace
Then I reffered to below link and followed the steps as mentioned by Johannes Fahrenkrug
How do I change my iPhone App binary filename
It finally worked and finally my app status changed to Waiting For Review
Hope this helps all.
Related
This is about the 5th time I have deleted all certificates, made new ones, republished, and tried to load. I seem to get the same errors every time. I am sure the provisioning and certificate are for distribution and not development.
It seems only one little section of the adobe help mentions the zipping and unzipping. Is this hackish method really working for people? Is the ipa the only file including in the zipped folder?
When I do this, unzip it, and go into the payload folder I see the file APPNAME.app, but it looks like a piece of paper with a big white circle with a line through it. When I try to click on it the mac says, “can’t open this file”
Is this normal? I zipped it and tried uploading but I am still getting these errors:
Unable to extract codesigning entitlements from your application. Please make sure rufood8 is a valid Mach executable that’s properly codesigned.
Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an Iphone distribution certificate.
I've recently upgraded my Mac to Lion, and also Xcode 4.
In Build Settings, I've set "Code Signing" for "Release" to be "iPhone Distribution" which matches our Ad-Hoc provisioning file (which we've used in the past, on Snow Leopard/Xcode 3).
I have deleted the old Entitlements file (as it's apparently no longer used by Xcode 4).
In the Scheme section, I've set Archive to use the Release build.
I'm building with Product > Archive.
I'm saving the file by going into the Organiser and clicking Share, then making sure the same Ad-Hoc provisioning is selected.
I'm sending the resulting IPA file to my boss, who has previously installed this app. When he tries to install it, he gets the message "[appname] could not be added to your itunes library because it is not a valid app".
I've been trying every combination of settings I can think, but we just cannot get this to work. I can find this error only twice in Google - once from someone with a jailbroken phone and another posted in comments of an article, someone having the same issue, but there are no responses.
Any help would be really appreciated.
Edit: Same thing happens trying to drag the IPA into iTunes on the Mac that created it! :(
Edit2: Just taken another (almost identical) project and tried a build without "Modernizing" the project, or selected any of the new options in Xcode (icons, launch images, orientation etc.), and this build works. I'm going to work through each of the things I did with the original app with this one, testing at each step. Hopefully should be able to isolate which step is breaking the compiled app!
(also posted to Apple Dev Forums)
I believe I've tracked this down... It seemed to be happening really intermittently, so it's taken some time (I'd reproduce it, roll back the change, confirm it worked, then re-apply the change, for it to then work again!).
However, after much cleaning/restart/etc., I believe it's related to the "Build" version in the target settings (there are now two version fields, "Version" and "Build"). It seems that if "Build" is blank, then this error occurs.
Unfortunately, changing this value doesn't seem to rebuild properly, so sometimes if you change it, then Archive, you still get the previous value. Manually cleaning before Archiving seems to work around this.
The value gets written into the plist file as CFBundleVersion.
Recently I suffered a problem with an Ad-Hoc installation using TestFlight service, the message in the log didn't help too much:
Jul 25 12:52:39 MyiPad installd[477] <Error>: 0x10059c000 init_pack_state: Archive we've been requested to install is 0 bytes. That can't be a valid ipa.
After many tests, I found this question and the problem was the same, the Build field was empty (this answer save my day :-) )
So, if anyone else has this problem on TestFlight, I hope my answer allows to find this page easier ;-)
I also faced the same issue. After doing some research found below answers as:
App Version and Build version should not blank.
Don't put special characters in my app bundle name.
And also there was no issues with my provisioning profiles.
After debugging found that there was name mismatch in my scheme name and info.plist file name. In my project, I have 3 schemes like a,b,c and only one a-info.plist file. I was creating IPA for different scheme like 'b'.
In your scenario, if you have created multiple schemes then check your Info.plist name. That should have to be same as your scheme name (for which you are creating an IPA).
Example. The scheme name is 'myScheme' then your Info.plist file name as 'myScheme-Info.plist'.
Hope this will help you.
I got the same message ("not a valid app"). In my case, I was FTPing the built app to a web server then I would be able to OTA provision it. I was not swapping to binary mode before I was putting the file, so the .ipa file got corrupted on the way. Took me most of the evening to figure that stupid mistake out...
ok.. do one thing.. Open info.plist.. Go to bundle identifier and change bundle identifier name. It needs to be unique.. something like "com.yourcompany.projectname" and create and try to install the ipa.. It should work
I came across this question while researching a similar problem so I'll answer here even though the cases are not identical, because others will search for the same error message.
I had an ad-hoc app that everyone in the development team could install fine, except one person, who got the error from iTunes:
X is not a valid app
He had been able to install earlier versions of this app. Rebuilding the app, changing the version number and changing the build number had no effect, he still could not install but others could.
I fixed it by creating a brand new Xcode project, either copying the files or copying and pasting the content of the files from the old project to the new one, and rebuilding the app and signing it in exactly the same way as the old project. It worked.
I had a similar issue while trying to create an .ipa for adHoc distribution for one of the Old project (built a year ago by ex-developer). After a lot of research in google and following the above solutions it didn't worked out for me somereason.
Later after following this link - here. By replacing the .plist file with the existing working projects (obviously - the relevant icons/bundle display name/identifier) and renaming with the current .plist name. It worked for me.
I literally spent about 3-4 hours to fix this issue. Hope it helps some one.
environment was native - iOS app.
add......
"Application requires iPhone environment" in your info.plist or if added give it value "YES".
Check "Build" and "Version" in general are not empty....
hope this will work
Importing the project contents in to a new Project solved the issue for me.
For me, we were trying to do an enterprise build of a very old app, from iOS 5.
After confirming profiles and everything else was fine, debug builds work correctly, I noticed the general consensus was around issues with the info.plist file.
I compared the info.plist with another app and sure enough,
Application requires iPhone environment = NO
Basically this key needs to always be set to YES for iOS apps regardless whether its for iPhone, iTouch or iPad...
It may not be limited to that key for everyone but make sure the info.plist looks similar to working apps.
Bundle version
Bundle versions string, short
should always be present!
right.. but I guess it is clashing with earlier bundle identifier( this happens because you have upgraded the Xcode). Did you try and change the existing bundle identifier name and install ? I had identical problem and wasted 3-4 days.. I changed existing bundle identifier name and it worked.. Also you may want to check Bundle name and Bundle version are present in info.plist
In order to distribute my iPhone for test purposes on a couple of device Over the Air, I have created an AdHic distribution profile and followed the explanation I found in this blog (sorry it's in French but the screenshot are quite detailled):
http://www.media-business.biz/content/iphone-cr%C3%A9ez-votre-propre-appstore
I install the position profile on the device from my web site but when it comes to the application I have an error message saying it's impossible to download the app.
Is this a known problem ?
Thanks a lot for your help.
Regards,
Luc
ps: just adding a last minute question... is there a place I could see some error logs ?? :(
Here's another explanation in English. This distribution method only works with devices running iOS 4.x
Make sure that:
The IPA file name matches exactly the name of the server (case sensitive).
The bundle version number is identical in the IPA file and your plist file, and that you update it every time you make a new IPA (or the phone will think it's already installed and not update)
You are using an itms-services:// link to point to the plist file, and the plist file has the correct URL to your IPA file.
When you go into Organizer and press the "Share" button, you select exactly the distribution profile you intend to use (sometimes I think it can select the wrong one with automatic).
I had this exact same issue, and it was because I hadn't installed an AdHoc mobileprovision file and was building against my Dev mobileprovision. Check that first.
I finally found testflightapp.com, that is really great !
I also think testflightapp.com is the most convinient way to do this, as long as the beta testers you'll contact accept to sign up there. The great additional value is that if you install their SDK in your app, you'll be able to monitor the activity of your beta-testers (for instance you can define waypoints with definite names).
However, if:
You already konw the UDIDs of your beta testers
You just want them to be able to click on a link from your server to start installing the app,
You don't need "in app" follow-up and just request feedback from your testers,
Then I strongly recommend this tutorial:
Whenever I submit my app to itunesconnect, after about 10 minutes, the status changes to "Invalid Binary" with absolutely no explanation why.
I have searched all over for answers there is non. I even re-installed XCode and App loader.
Note that App Loader doesn't give any errors whatsoever.
I build with XCode 3.2.3 iPhone 4 GM Seed iPhone 4 based SDK iPhone/iPad as a target family
I had the same INVALID BINARY error from iTunes Connect even if Application Loader accepted my binary. The solution was very simple...
Open your info.plist, right-click and check Show Raw Key/Values:
CFBundleIconFile = Icon.png (my iPhone 57x57 PNG icon)
CFBundleIconFile~ipad = Icon-72.png (my ipad 72x72 PNG icon)
CFBundleIconFiles = array
Item 0 = Icon.png
Item 1 = Icon#2x.png (my iPhone 4 114x114 PNG icon)
Item 2 = Icon-72.png
Save, clean all targets, build and analyze, compress in Finder and resubmit!
The error was caused because I typed the key "Icon Files". In Raw view, this has mapped to "Icon Files" instead of CFBundleIconFiles. I have Xcode 3.2.3, I guess Xcode 3.2.4 better maps this key identifier.
Good Luck everybody!
Source: Technical Q&A QA1686: App Icons on iPad and iPhone
The "invalid Binary" did cost me 4 days to figure out. and because I stumbled over this helpful page, I want to help saving you the valuable time. In my case, in the provisioning portal, a colleague revoked the distribution cetrificate, built a new one and did not let me know. You can use the new certificate for making new prov files, and in the build process, xcode "thinks" everything is all right. which of course is not. Only after uploading to the itunes connect you see the "Invalid Binary" note without further explanantions. The solution was to revoke the certifikate (again) with the whole certificate request procedure and make a new one. Use this as the certificate, and you will be fine - no more uncommented "Invalid Binary" - and if you share tzh eteam agent access to the portal with others, make sure, you let them know and hand over your new .p12 key file.
The topic is old but i had the same problem today and maybe my explanation will help somebody in future.
While submitting app by Xcode 4 organizer you have to choose distribution profile. Make sure this is exactly the same profile which you set in build settings (project and target). For almost all my projects i didn't have to change build settings from development to distribution and it was fairly enough to choose distribution only in organizer while submitting. But in one case this resulted "Invalid Binary" error in iTunes Connect.
Apple has improved the error reporting on this recently and now you will get an email that highlights the problem accordingly. Just be patient it may take a few minutes to come in. I received the following email which highlighted the problem:
Dear Developer,
We have discovered one or more issues with your recent binary submission for "XXX.APP". Before your app can be reviewed, the following issues must be corrected:
Invalid Icon Path - No icon found at the path referenced under key "CFBundleIcons": xxxIcon.png
Once these issues have been corrected, go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.
Regards,
The iTunes Store Team
I had this same problem and here is how I resolved it:
The CFBundleIconFile is not listed instead Icon File and Icon Files. Change the Icon File to the Icon Files selection. Now click the left arrow next to the Icon Files label to expand the list. You will see Item 0, select Item 0 and then click the plus button to the right to add another item. You should then see Item 1. Enter your 56x56 icon file name in Item 0 and your 72x72 icon file name in Item 1. Save the info list
Since I want this app to be both Iphone/Ipad I choose:
Architecture as Standard (you will get a warning but if you change to only armv7 for a no warning build, the binary will be rejected by itunesconnect)
Base sdk as 3.2
Target Device family as Iphone/iPad
iOS Deployment Target as 3.2
Now build for app store distribution, compress and upload to itunes connect.
I had the same problem. App stucks in "Upload Received" status for more than 5 days. After contacting the Itunes Connect Support with the topics "Manage Your Applications" and "Upload received" and answering unnecessary questions, the App Status changed back to "Invalid Binary". After searching for solutions which recommended to check the icons files I found another tip to check the certificate.
That was my solution: I recreated a distribution certificate with Mac's KeyChaining tool and now used a RSA private key instead of DSA. That helped. I re-uploaded the App and the status changed to "Waiting for Review" few minutes later.
I came here for the same issue, tried the App Launcher update, et cetera. I tried rebooting and resubmitting a dozen times, manually editing the info.plist again and again. For me the solution was noticing that there is now an "Icon files" AND and "Icon files (iOS5)" entry. Check both of these for a bad reference to moved icons.
Did you zip the binary? Might want to try that.
From the iTunesConnect Developer Guide:
Application Binary and Small App Icons
Keep the file size as small as
possible, both for ease of upload
through iTunes Connect, and for the
end-user’s purchase experience. The
binary must be a zipped file, and pass
a code sign check upon upload in
iTunes Connect.
iPhone and iPod touch:
If you are uploading an app to run on
iPhone and iPod touch, the binary must
include an icon that is 57x57 pixels,
which will be displayed on the home
screen and the App Store when viewed
from the iPod touch and iPhone. You
can also optionally include a hi-res
icon that is 114x1144 pixels to take
advantage of the Retina display on
iPhone 4.
iPad: If you are uploading
an app to run on iPad, the binary must
include two icons: one that is 50x50
pixels and one that is 72x72 pixels,
which will be displayed on the iPad
home screen and the App Store when
viewed on the iPad.
If all else fails, reboot, reboot, reboot. I ended up rebooting and resubmitting five times (making no other changes, honestly) before my app was accepted.
A couple of other things to try.
if you have an old xcode 3.2 Entitlements.plist file hanging around.
Delete it and recreate > New File > Code Signing > Entitlements.
Check the configuration for Archiving
Product > Edit Scheme > Archive > Build Configuration
Make sure the correct one is selected. (for me Release was selected but I needed Distribution profile - yours may vary)
your Binary final rejected because of some basic reasons.
like,
1)Check For 'icon files' option in info tab of project.
if your app is Universal icon files should be 4 or <4 *must not more then.
if your app is for one device only the icon file should be 2 or <2. *must not more then.
Icon files should be as per itunes Guide. itune guide Link
2)Must check that for splash screen if your app does not have any splash then also give blank splash screen.in universal set for both device.
3) if you are updating app then check for binary version of previous uploaded app and your app.your app must have grater version then uploaded.
4) check for Bundle name and version also.
I tried to upload my iPhone application to the App store, but received the following error: The binary you uploaded was invalid. The icon file must be in .png format.
The icon file IS in .png format, size 57x57, so assumed it is a bug and tried to upload with Application Uploader, when I got another error:
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate.
I followed every single step, and it is not working... it is driving me crazy! Please advise what should I do!
First, check that the icon file is in .png format, rather than .PNG format.
Second, take some deep breaths, look out a window for a few minutes, and then go back over the steps to upload your iPhone application.
Many people were confusing (like me) modifying the code signing property of XCode.
You must ensure that your code signing identity property start with
iPhone Distribution : Developer Name
instead of
iPhone Developer : Developer Name
PS : If you have no option start with iPhone distribution, you didn't get production certificate yet.
Since you haven't mentioned anything regarding the fact that you did sign the code, I'm going to assume you didn't.
You'll need to get your application code signed in order for it to be accepted, so that the phone knows it's from a trusted developer, and not just a virus someone has uploaded.
Do you have a code signing certificate?