I am currently having issues validating and uploading my Xcode to itunesconnect. I have done it plenty of times before with other build numbers and now all of a sudden it will not work. I am using an opensource framework called SCLAlertView. Uploading my project with that framework in the past was fine but now it will not work. I have searched through just about every related thread from google and could not find a solution. The exact error is "Archive validation operation failed due to the issues listed below. iTunes Store operation failed. No suitable application records were found. Verify your bundle identifier 'org.cocoapods.SCLAlertView' is correct." I tried messing with the code signing identifier and provisional profile settings but nothing seems to be working. Also I would like to emphasize that the error is only given for the SCLAlertView framework, not my main application. I would appreciate any advice on how to fix this issue. Thanks in advance.
I recently made some changes to my iOS app.
Now I want to push the new files to iTunes Connect and I keep getting "ITMS-90035 Invalid Signature. Code is not signed at all."
I found answers to similar questions here on StackOverflow but I there was no solution provided that worked for me.
Here is what I tried:
I tried to reactivate my certs / provisioning profiles to make sure they are valid and configured for deployment
I checked for .sh / .git files as mentioned here - but couldn't find any
I checked my build settings as mentioned here
I checked for external libs but I'm only using GoogleMobileAds and GoogleAnalytics - both worked in my last submit (this issue was mentioned multiple times with different external libs)
Any idea where to search? Sadly iTunes Connect doesn't give any feedback about which file makes the problems.
I noticed you tagged this under swift2. Are you using a beta Xcode to build and submit to the App Store? That's not permitted.
Crazily, I was able to fix this by unchecking the Include Bitcode ? checkbox when uploading via Xcode 8.1 (8B62). ENABLE_BITCODE is set to YES everywhere in my project, so I'm not sure what's going on here.
Will report back once it's sorted.
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...
I am writing because I have a serious problem - I have bought the Commander Cool game on the cartoonsmart site. However, a serious problem occured. The application cannot be accepted by the iTune Connect validation. I tried to publish it from two different developer accounts and the error still occurs. The error suggests some problems with the certificate but I am sure it is 100% right because I have published more than 20 apps in the App Store as for now. I ask you for help because you are my last hope. The only thing I changed was to add armv6 in Valid Architectures because without it the app could not load.
Error is displayed via iTunes Connect:
"The following issues were found during validation:
Apple's web service operation was not successful
Unable to authenticate the package: 721772200.itmsp
ERROR ITMS-9000: "The bundle 'com. . ' at bundle path 'Payload/CommanderCool.app is not signed using an Apple submission certificate." at SoftwareAssets/SoftwareAsset (MSItmspSoftwareAssetPackage)?
Maybe you have additional errors like a missing 120x120 icon, if that is the case you should follow this
'Missing recommended icon file - The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format'
Fix other problems and then you could be able to submit your app, I was having the same problem.
Check the icon file name in Plist file. This may be occur due to wrong icon file name.
Move your icons and splashs to asset catlogs.
I was also facing this problem in xcode 5, actually i was trying to build code which was written in previous version of xcode (4.3 i guess).
I had the same error. In my case, the iPhone 5 was conected.
Steps:
Disconnect the phone.
Select IOS Device (in simulators).
Then archive.
Recently I created an application for iPad. I created the binary(something.zip) and uploaded that via Application Loader, but the result of uploading was 'Invalid Binary' always.
and I received this email from apple when my app was denied from them due to the issue 'Invalid Binary' :
"Invalid Signature - Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target."
I searched the web from around the world to solve this annoying problem, but I cannot see the good answer. Here's the data of my application's info.plist :
Localization native development region : English
Bundle Display name : $(PRODUCT_NAME)
Executable fike : $(EXECUTABLE_NAME)
CFBunldleIconFiles :Icon-Small.png(29x29), Icon.png(57x57), Icon-Small-50.png(50x50)
(all files were created as 72ppi, RGB, flattened, No transparency)
InfoDictionary version : 6.0
Bundle name : $(PRODUCT_NAME)
Bundle OS Type Code : APPL
Bundle creator OS Type Code : ????
Bundle Version : 1.0
LSRequiresiPhoneOS : Enabled
UIPrerenderedIcon : Enabled
UIApplicationExitsOnSuspend : Disabled
UIStatusBarHidden : Disabled**
and I created this application with these tools -
cocos2d Ver0.99.4-rc3 /
xcode Ver3.2.5 64-bit /
iOS SDK 4.2
I tried to solve this problem for 3 days, but I couldn't.
Is there anybody who can solve my application's problem, It's an emergency issue of our company.
Thanks everyone
It seems like there are a LOT of causes for receiving this cryptic and mostly unhelpful email. Even after verifying the use of distribution certificates, cleaning & rebuilding my project, and checking with codesign from the command line (and following instructions from the email), no errors showed up—-but I'd get the "invalid signature" email right after uploading. All the solutions seem anecdotal and obviously depend on what secret error is causing the problem. I've spent the last week pulling my hair out, trying to figure it out for my app—-and finally got it successfully submitted today—so let me share my story and see if it's relevant to your situation.
In my case, I seemed to have a complex cause of having my Entitlement.plist set with an incorrect variable along with the holdover of an old provisioning profile (from a previous Xcode version?) buried deep in the project.pbxproj component of my Xcode project file.
The "aps-environment" variable in my Entitlements.plist was set to "distribution" instead of "production" (I swear I read somewhere in the developer docs that it was supposed to be "distribution"!) But fixing that alone wasn't enough to get my app through. (I must have submitted 100 different combinations of app configurations trying different variables!) Starting with the helpful suggestions from this post on another forum, I dug through the distribution profile and found duplicate entries for some variables. The duplicates had empty quotation marks (i.e. nothing set for the variable) or strange variables or old provisioning profiles which seemed to be causing problems (somehow). Cleaning this up and removing the duplicate lines with bad variables worked in my case. YMMV. But carefully examining the project files ("show contents" on the Xcode project file in finder) seems like a good idea for diagnosing. Good luck!
This is a very annoying issue, I spend a lot of hours in trying to find a solution but at the end this was corrected for me by removing the Entitlements.plist (as I understood it is only needed when deploying for ad hoc), removing any duplicate field in the Info.plist, setting the target to "Distribution" with the correct configuration of the certificates and using the method of "Archive" then "Validate" and at last "Submmit" in XCode