Related
I submitted my app in the App Store. First I validated it, and turns out successful. Then I submitted it and succesfully uploaded to iTunes Connect. After a minute, it says that the file is Invalid binary. I am uploading an update of an existing app which is already published in the App Store. (previous version uploaded by other developer). I tried every solution that I found in google search but no luck.
Just for information.
Today I faced the same problem of Invalid Binary while uploading new version of existing application.
I got following email from apple
iPhone 5 Optimization Requirement - Your binary is not optimized for
iPhone 5. As of May 1, all new iPhone apps and app updates
submitted must support the 4-inch display on iPhone 5. All apps must
include a launch image with the -568h size modifier immediately
following the portion of the launch image's filename.
Launch images must be PNG files and located at the top-level of your
bundle, or provided within each .lproj folder if you localize your
launch images. Learn more about iPhone 5 support and app launch images
by reviewing the iOS Human Interface Guidelines and iOS App
Programming Guide.
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." You can then
deliver the corrected binary.
Solution:
Added 4inch app screen shots in iTunesconnect meta data
Added Default-568h#2x.png image in my application for iPhone 5
After these changes application successfully submitted.
Need to add arm64
I faced the same problem of Invalid Binary while uploading new version of existing application.
The reason are from February 2015 itself we need to Add arm64 to our app. i added this then my app successfully upload to app store.
Try to check the provisioning you made for the itunes store are correct with your application.
Remove the old binary which has been rejected then add the new one.
If you can do try to make fresh provisioning and also check in the xcode as well.
And do check the mode,is that debug or distribution as you need to make the build for distribution.
Hope it man help you.
Cheers
Sanjay
You cannot submit an app that uses the same bundle ID or the same app name of any app (even the "same" one) submitted by another developer account.
Make sure you have choosen "App Store" as distribution method in distribution provisioning profile, not "Ad Hoc".
I have faced this issue many times.My app got passed validation and submitted
successfully to iTunes Connect.But It shows invalid binary in prerelease
options.I saw one awesome post in Apple discussions and finally solved my
issue.App bundle id was changed in config file of my web app.I have changed
old bundle id in config.xml and app uploaded for review.
Try using the Application Loader under /Developer/Applications/Utilities. Make sure you have created a New App in iTunesConnect...under Manage Applications, select the application you are going to create an update for... when that loads on the right you will see Add a New Update.
Anyone having problems deploying Enterprise apps on iPhone/iPads running the released version of iOS 5 using the OTA ("over the air") methodology?
During the installation process, we get the alert box: "the app could not be installed at this time". Tapping the Retry button does nothing. In some cases, repeated tapping of the Retry button eventually results in a gray, empty launch icon being left on the home screen. No app installed. No other errors.
Anyone else seeing this or have a resolution?
The below description is a bit involved, but please bear with me as it may help others who run into the situation. I will post the resolution if get a resolution from Apple. So far, no joy there.
Our app refuses to install OTA on iOS 5. This same app WILL install on iPhone/iPad devices running iOS 4.x.x AND the same app will install on iOS 5 devices physically connected to a desktop machine using the iTunes app.
The Apple Developer forums under the IOS 5 Beta category complained about the problem but no indication of resolution as of last week just before the official release of iOS 5.
Cookies are set to be accepted.
Bowser cache and history cleared.
Using mobile safari originally installed with original iOS version 4.x.x.
System hardware and operating system configuration
iPad 2, iPhone 4 or any iPhone device running iOS 5 RELEASED version.
Browser and version
Mobile safari that is installed with iOS 4 on ipad2. Don't know if mobile safari upgrades with ios 5 upgrade.
Using a corporate wifi network. Yes, we are behind a firewall and use a proxy server. Since iOS4 devices install without problems, I don't think installation being blocked by the proxy or firewall.
Enterprise app built with Xcode 4 and ios5 sdk provided with it. Built to be backward compatible with iOS 4.0.
Distribution provisioning profile is correct as we have been using it for several weeks.
This app installs properly on iOS 4 devices both over the air and via iTunes application method.
This app installs properly on ios5 devices through the physical connection with iTunes application on the Mac desktop.
Steps to reproduce:
User types in the URL in mobile safari on iPhone/iPad running ios5.
The resulting webpage shows the download app link.
User taps on the link and is asked if they want to install the app.
User taps the yes, install button.
App proceeds to install.
A gray launch icon shows up on the home screen with the progress bar empty at the bottom of the icon.
Message below the icon indicates "loading".
Seconds later, user gets the "cannot download app at this time" error message as seen in screen shot attached.
Tapping the retry button results in the same action just described.
Tapping done results in the download stopping.
If you tap retry several times, user sometimes is left with the gray empty launch icon, which will not launch and cannot be deleted.
Note: In the apple developer forums, under the iOS 5 beta category, people are describing the exact same problem with no resolution.
Had the same problem, and was able to resolve it. However, the error noted is not specific to a single cause that handles every case... some detailed investigation needs to occur.
Your best bet is to connect the device to your Mac, and using the Organizer of xCode view the console logs while you are attempting to do a wireless deployment. There will be some useful information available -- please post the logs.
For my case -- the icon files were missing from the build, as a result of moving from xCode3 to xCode4 and also, the distribution plist was referencing an image that returned a 404. Both were logged in the console, but not very clearly.
Also, as a sanity check, manually verify the URL to your IPA file also.
I had this same problem and was sure everything was correct in my project; but restarting Xcode and doing a clean revealed my Enterprise scheme had somehow defaulted to the wrong provisioning profile.
Re-selecting the correct profile and re-archiving the app fixed the issue for me, I'm able to install an enterprise app on both iOS4 and 5.
I wanted to chime in after fighting this for a few hours. It is iOS 5 specific.
We had an htaccess password protection on the directory. Removing this allowed the app to finally download. So if you have htaccess, perhaps you can point the user to a parent directory that is password protected, then navigate to the subdirectory containing the app that isn't password protected. This is a temporary solution, apple needs to fix this.
Another thing to consider is the URL you specified in your over-the-air Application.plist file. I received the same error message ("-application- could not be installed at this time") because the URL I specified was too unspecific. Rather than writing "directory/directory/application.ipa", I had written "directory/directory/". You must include your application in the complete URL of the plist file's configuration.
If you didn't do this, don't fret! You don't have to rebuild the entire thing from step one, you can open your .plist file in any standard text editor and simply change the URL.
We had the same thing.
Our mistake was to point to a wrong 512.png icon in the manifest.
Which was no problem on iOS4 but turned out to stop iOS5 into a "...at this time" alert.
Wanted to chime in on my experience.
In my case, we were changing the address where the IPA file was hosted. Although I updated the PLIST file with the proper URL to the IPA file, iOS was still going after the old URL almost as if it cached the PLIST data. Creating a copy of the PLIST file and renaming it resolved the issue (data within the file remained unchanged)
I met the same problem today. The app can be installed in ios4, but failed in ios5 with "** could not be installed at this time" alert.
According to patricksan's suggestion, I download iPhone Configuration Utility 3.5 for Mac OS X, and try to catch the log while install the app through OTA.
The log helped me finally, one sentence of the log says entitlement 'get-task-allow' has value not permitted by a provisioning profile. It remind me that if the code signing identity in build settings of Project and Targets are correct, after checking them in Xcode, I found the code signing identity are not correct one, they should be iPhone distribution:.... other than iPhone developer:..... After correcting them, and re-Archiving the ipa file, it can be installed in iOS 5 now.
Check your Info.plist for Required device capabilities property. I recommend to delete completely this property if you haven't any restrictions on use.
I am trying to submit an app to app store through application loader. However, I am getting a message that "no application found in archive", from the loader. I have mode sure that my application is ready for upload and bundle-id matches given in the app summary. What can I do?
Have you tried uploading directly through XCode? If you're having problems with the application loader it's worth trying the alternative route. Once you've built and archived your project, go to the XCode Organiser, select your chosen app archive, and hit the 'submit' button. That way you can be guaranteed you'll have the right binary.
I stopped using the application loader a while ago once XCode got the ability to submit straight to the app store.
I have created a new version of iPhone app. I wanted to change the icon, so:
I added the icons in different sized to the Resources folder of my Project in XCode:
I specified the icon files in the info.plist file:
in iTunes Connect I added new version of my app and replace the old icon with the new one. The new icon is now visible when I log in to iTunes Connect.
The effects:
I can see the new icon when I run my app on simulator.
I can see the new icon when I visit AppStore with iTunes on my Mac.
I can see the OLD icon when I visit AppStore on my iPhone.
I can see the OLD icon on my iPhone after upgrading my app to the new version.
Any ideas why the old icon is still visible in some of the places?
kind regards,
Jakub
Use "Build > Clean all Targets" and then build and run. Xcode doesn't always see that images have been updated, and leaves them out of incremental builds. Cleaning before building makes Xcode build the app file from scratch, and will pick up any images it's failing to get.
Why it's inconsistent is that different build types (simulator vs device) are different build targets, and got built with different versions of your images. Not unusual.
The one thing that this WON'T address is the old icon on the iPhone's app store app. You might need to update your app store submission with fresh images.
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.