I have made a game using game maker and successfully got it exported to xcode 5 on my mac. I have also successfully played the game on my iphone, so the game does work quite well.
I do have the provisional profile, the certificates needed (developer and distribution). I only have my certificate once in my keychain.
I also created my app on the developer website where it is now ready for upload.
Whenever I try to upload I can select my app and it starts uploading, only after a short time I get the error:
ERROR ITMS-9000 The bundle "com.grown-apps.whopays" at bundle path payload/whopays.app is not signed using an apple submission certificate at softwareassets/softwareasset (MZITMSPsoftwareassetpackage)
But I have signed everything in xcode 5. I selected the distribution profile to sign with.
It doesn't matter how I try to upload, using application loader or xcode 5, I get the same error.
I have now tried for a WHOLE WEEK searching the internet, and I just now got to the end where I simply cannot stand this anymore. I have followed every video or text guide I could possibly find. I have found many people with the same issues both here and everywhere else, none of the solutions people came up with and worked for many just didn't work for me.
I am now sitting here at 3 in the morning almost bald from ripping off my hair in desperation in hoping that someone somewhere has ANY idea what I can try next, this really is my last cry for help. I have used more than 100 hours just researching on this problem and it has turned up nothing for me.
Please help me so I don't have to take the final step and throw my expensive mac out the window!
I had this exact same problem and just resolved it today. In order for me to get anything from Windows to the Mac via Game Maker Studio, I had set the certificates "Trust" setting in the Keychain Access to "Always Trust" for both the provision and the distribution.
HOWEVER, for the app store submission, I had to change the "Trust" setting back to "Use System Default" for both the certificates. Also the keys attached to the Certificates are always put on "Allow all applications to access this item" in the "Access Control" tab of the respective key, regardless of the Certificate "Trust" parameter. I hope this helps people in the same bind.
Related
I am getting message "TestFlight is Currently is Currently Unavailable. Try again later" when trying to install from TestFlight app. My outside testers get a message "[App Name] beta has expired" when trying to run the app. When trying to renew from TestFlight they get "TestFlight is currently unavailable. Try again later." I've been trying again later all day and just wanted to see if anyone else is experiencing this.
I had this same error.
Discovered that the company certificate was expired, and therefor all provisioning profiles as well.
1. Renew the company certificate (download, install on your computer)
2. Renew the provisioning profiles (edit, select new valid certificate, generate, download and install in xcode)
3. Repost the app to iTunes connect
problem solved :)
If you're new to Xcode, be sure to note the difference between a CERTIFICATE (first large red arrow below) and then a PROVISIONING-PROFILE (second large red arrow below). Basically provisioning-profiles are made using a certificate. So first make a new certificate, and then set a provisioning profile to use that certificate.
First, certificate...
Then, provisioning profile...
In the second image, click on the "Distribution" provisioning profile (the one with the purple arrow.) Then click to edit it, and you will then see the third image below. Note that somewhat annoyingly, the DATE is the only way really to distinguish your corporate certificates, when, you have more than one. (Ultimately you can, generally, just throw away the OLDER one, but it's clearer if you leave it so that you can clearly see how you select one or the other, as in this third image.)
Editing a provisioning profile...
A minor point is that you'll have to make a new build (so, increase the build number in Xcode, then archive, and then send up that new one) because you'll get a "redundant build" warning if you fix the cert/profile (i.e., as described in this answer) and re-submit.
Another possible reason for this message:
You accidentally removed the affected user from the TestFlight external testers group.
Adding him again would fix the issue.
Problems with certificates have been identified in several answers as the cause to this message. However, there's another possible (yet stupid) cause that leads to this situation.
You may see this error if your device's date/time is not set correctly. So make sure you set the correct date or "Set Automatically" is enabled under Settings > Date & Time.
I spent 2 days "trying again later" until I realized this.
I was ultimately able to fix this message by uninstalling and reinstalling the TestFlight app from scratch. Worth a try if the other answers don't fix your problem.
Make sure TestFlight can use Mobile Data if working without Wi-Fi. Otherwise it fails with this generic error.
Had to disable 'Use cellular data' option in Settings for Testflight. I did not have cellular data internet and was connected via wifi. Looks like testflight tried to use cellular data with that option being on.
Did a factory reset and that fixed it for me.
Actually just waiting solved the problem.
I had to wait around 16 hours and then it worked normally, without doing anything particular.
Sometimes the error message is just what it is, no need to panic !
Ahh devs ;)
Currently, Testflight is experiencing issues. It's always worth checking Apple's status page
Another possible reason , if your mobile app build is in processing state for a long time.
Just wait for the build to complete apple processing solved our issue of Testflight currently unavailable.
I had this same issue when using my personal email for beta testing my app, then using my apple ID email for internal testing.
I solved this issue by removing my personal email from all testing tracks, then deleting the TestFlight app and downloading it again. I now only use the one email (my Apple ID) for all testing.
I had to go to https://developer.apple.com and accept a new version of Apple's Developer Agreement
When I ran into this issue, my first thought was to search Stack Overflow for solution. I did the search, found several topics. But, unlike my issue, those posters got some clue from the error such as,
App Store error: The binary you uploaded was invalid
Invalid iPhone Application Binary
Uploading Binary iPhone App "The signature was invalid" again again and again
The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate
Or this one:
"The binary you uploaded was invalid. the file was not a valid zip file" Error message uploading app to iTunes Connect
The binary you upload was invalid. the file was not a valid zip file
Or this one
CFBundleVersion in the Info.plist Upload Error
The binary you uploaded was invalid. The key CFBundleVersion in the Info.plist file must contain a higher version than that of the previously uploaded version.
But for me, I got nothing, it just says ERROR ITMS-9000: "The binary you uploaded was invalid"
I try to resolve this issue by the following attempts, all of them failed
Test on simulator make sure the app works ... Check!
Test on device (iPhone 5S, iOS 7 and iPhone 4s iOS 6) to make sure the app works ... Check!
Clean and build ... Done!
Make sure that I'm using distribution profile (not ad hoc, dev) ... Check!
Redo the whole process of certificate and provisioning profile ... Done!
Check my code signing identity ... Check!
Check bundle id, there are matches (Xcode == App ID in Apple Developer == App in iTunes Connect) ... Check!
App ID case sensitive check .... Check! (lower case, com.companyname.productname)
Delete target in project and then create a new one (I have one project, multiple targets) ... Done!
Delete scheme and then create new one ... Done!
Check icon size, check loading image size, check pixels per inch ... Check!
Check Localizable.strings for typo ... Check!
Delete build foler ... Done!
Restart Xcode, restart computer ... Done!
Connect to another wifi router ... Done!
Submit from my colleague Macbook ... Done!
Create new App ID, new certificate, new provisioning profile and update iTunes Connect Bundle ID ... Done!
Take a break for an hour, try again ... Done!
I really have no idea what did I do wrong. I've been submit app since iOS 4, hundreds of updates. But never ran into anything like this. In fact, I've just update another app yesterday which share the same codebase with this one, no issue at all.
Is there a way I can gather more information about "the invalid binary" Xcode is telling me? Or is there anything else I should try?
For everyone who found this topic (18 July 2014), maybe your best shot might be, taking a break for few hours (or a day) and try again.
--- Last Update ---
It turns out to be Apple Server issue
Says, I have an application called "Sample App"
This app has an app id of com.tartw45.sampleapp
This app use an App Store Distribution profile called "Simple App App Store Distribution Profile"
Back to last Friday (18 July 2014), everything seems ok, no indicator of any error but I couldn't publish the app as I stated above
Today (21 July 2014), I tried again with archive from last week, still no success.
I decide to redo the archive process and I found that "Simple App App Store Distribution Profile" is no longer valid
I login to developer.apple.com and found that "Simple App App Store Distribution Profile" also no longer there in the list of all provisioning profile. **
Then I try to create a new provisioning profile with the same name (Simple App App Store Distribution Profile) but there is an error says that this profile is already exist, please choose another name **
So, I create a new provisioning profile with slightly different name, refresh the provisioning profile in XCode, archive again and then publish .... Works!
So, It's definitely Apple Server issue and your provisioning profile (**), it has nothing to do with your XCode version or project setting (if you successfully submitted your app once before running into this issue with no reason). So, anyone who found this topic, please try to validate your provisioning profile and try to publish again.
I was having the same issue since last night and finally got it to work just now. Had to go through this process
Logged in on https://developer.apple.com> > Certificates, Identifiers & Profiles > Provisioning Profiles and revoked my company's Distribution Certificate.
Then Xcode > Preferences > Accounts > Apple IDs > (my company) > View Details and refreshed the certificates and Provisioning Profiles. It prompted that no Distribution Certificate was found on the Developer Profile and offered to request one on my behalf, which it did.
Launched Keychain Access > Certificates and removed all of the expired Certificates (somehow I had a few of them)
I went back to https://developer.apple.com> > Certificates, Identifiers & Profiles > Provisioning Profiles and edited all of my manually managed Provisioning Profiles (Development — which had to be re-generated — and Distribution — which had to be linked to the newly created Distribution Certificate and generated again)
Once again Xcode > Preferences > Accounts > Apple IDs > (my company) > View Details and refreshed the certificates and Provisioning Profiles.
Credit to Rodrigo on the apple dev forums
iTunes connect (or at least some services that iTunes Connect uses) are down for the moment, so "Take a break for an hour, try again ..." is your best shot. Apple of course doesn't update their status page until tomorrow or so.
https://developer.apple.com/system-status/
It's on Apple's side. I tried to validate a couple of apps that worked last night, no changes in code, credentials, or Xcode and this is what I get.
We found it wasn't necessary to revoke anything- when I went to Provisioning Profiles->Distribution, the two profiles for our two apps we were trying to release had been removed. I recreated those profiles (but I had to assign new names, using the old name led to a "profile already exists" message- so those identifiers are still out there- somewhere). Downloaded and installed the new profiles, resubmitted the archives we made on 7/18/14, and everything sailed right through.
Apple iTunes' Connect server is down at the moment. I have tried almost everything, but all failed.
I suggest as above to take some rest and try upload after an hour or so.
I ran into the same error when I tried validating my app. I got a message saying,
Unable to process app at this time due to general error
I searched on SO for this and only found a suggestion to wait for some time, as this is an error from Apple's servers. I tried all sorts of things, from playing with provisioning profiles to improving app performance and linking libraries, none of which resolved the issue. Unfortunately, I guess we don't have any other options than to wait and let Apple do its work.
Yesterday, I had to regenerate an expired distribution certificate and got errors each time. Now it works, but I got the invalid binary error. It looks like Apple have done some changes and missed up something.
There might be a link between a change in certificates yesterday and the invalid binary error today, which gives a possible explanation of this problem.
I've had the same issue and have found out that my Provisioning Profile for Distribution "somehow" disappeared from the Apple Developer Portal. But when I tried to re-create it, I received error message about the existing one (which I couldn't find at all).
Finally, I've just created a brand new Distribution Provisioning Profile, downloaded and installed it. In the end, I was able to validate the application package and upload was successful.
Just spent a while on this also, my upload previously worked and managed to get through validation.
However, once up Apple would fail/reject the uploaded binary due to something similar to the below
https://stackoverflow.com/questions/18952213/invalid-directory-name-your-app-contains-a-directory-name-that-is-already-rese#=
Upon retrying, later without making any modifications, rather then sucedding then failing after validation I started receiving an error exactly the same as the OP.
Fixing the framework reference issue, enabled me to succesfully upload.
So rather then uploading passing validation and then being rejected, it would not pass validation, and I give the same error, without any hints.
Hopefully this helps someone else.
In my case I updated my Mac version and it worked fine afterwards.
i am developing an native ios application on mac os mavericks image on vmware, i am doing a training in a company. this application contain PushNotification service. i have download a video tutorial and i complete all the tasks as the video show. but in the end when i install the provisioning profile it show this warning message : "valid signing identity not found" . i have work on this issue many days.
i am new in ios developing, so day by day i read questions of developers that have this issue also and i've read the answers and try to fix it but no result.
can anyone help me and guide what to do. down i will notice what i've see and i feel that this could be the problem and i can't do anything:
- when i create the provisioning profile , they gave me numbers of certificates to chose, none of these certificates is the one that i create.
There are probably many reasons for this message and many more potential solutions.
I often see this error message display when building. Quitting and restarting Xcode usually resolves the issue for me.
Have you tried downloading the provisioning direct from apple site? Sometimes I have problems when I try to update directly from xcode.
I know this is flogging a very dead horse, trust me I've gone through every question on here and tried everything that's been advised. No beans. I'm missing something my brain is not capable of seeing.
So, my app is ready for release version 1 (thanks for all the help btw) and I'm going through the pain of uploading it for Apple to reject ;) I started the app on another machine, so I exported my private key and imported it to my new system. I then created a distribution profile and installed that, only to get the message of hate from Xcode. After 8 hours of shouting I decided to revoke my certificate, delete all my profiles and go to bed. This morning I created a new developer certificate on my new system, created a new provision profile, and installed everything. I can run my app on my device, all good (in fact, better than good, some warnings vanished).
But, here it comes, I still get the 'no valid code signing' error when I create a distribution profile.
I've watched several Youtube vids, I do nothing wrong according to them. I read Apple's documentation (which let's be honest is a mess) and I did everything it told me, but it's so vague I probably missed something. And I read through everything I found here, to no avail.
Is there, somewhere, anywhere (please) a step by step walk through which is up to date? Every one I found was Xcode 3 or the screen caps from the dev centre don't match.
I'm going to be heading to the pub if anyone in London wants to join me and shout at Apple for making this such a mess.
Screen caps if it helps?
I find that this Ray tutorial is very well made.
OK, I'm leaving this here for other people who stumble across this nightmare and, like me, are a bit dumb/tired/lack caffeine.
After revoking and re-creating my developer certificate, I had not revoked and re-created my distributor certificate. I thought I had, the dates matched (today) but in fact I hadn't. I re-created that, and all was good. This may have been a bug, or it may have been me, or a bit of both. But re-creating the distributor cert AFTER re-creating the developer cert fixed it.
If you are getting this error after upgrading to iOS8 / xcode6, you will need to manually sign in with your appleID to the member center and downloaded the certificates directly. Then add them to your keychain and you are off to the races again.
After following the great tutorials from http://www.raywenderlich.com/ on how to submit your app to the app store from square one I started planning my beta test program.
I'm not going to get into details of everything that wen well but of what I'm dealing with right now.
I've read many many posts on how to create provisioning profiles for ad hoc distribution of my app to beta testers. I've focused on those helping user get the app over the air (OTA) after a forum recommendation.
I also know now that TESTFLIGHT is out there but I can't use it this time.
Everything works well except the part where the application actually gets installed on my device. I keep getting the error "Unable to Download Application" after a few seconds of pressing "Install".
There are several possibilities and combinations of certificates, profiles, signatures, and here is where I think I'm doing something wrong. I'd like to show you what I have and what I've done and maybe your experienced eyes can spot my missing step or misconfiguration.
On the iOS Provisional Portal:
1) Ad Hoc distribution profile with a couple of devices:
2) After I download and install my certificates (I've create a couple of each for testing purposes):
3) On my xCode's project configuration:
4) When I generate the archive:
5) I upload everything to my server and then try to get the .ipa to install on my iPhone (which is one of the two devices included on the profile)
And finally I get this:
What could be wrong?
The only difference I can see is in the CodeSigning, ensure both lines under Adhoc point to your certificate.
Second thing to verify: You did not mention the plist that is created during the "Save for Enterprice". Did you upload that to your server, too? And does your link point to this plist? Check out this answer for the plist stuff: How to send the build to already provisioned remote person's iPhone
I've had this exact problem even where, like you (as far as I can tell), everything is done right.
What I discovered is that if you've EVER had the url to the plist file or the app file incorrect then your iPhone will always fail to install. There's some kind of cacheing going on where the phone fails to download the updated plist file if it's previously downloaded an incorrect one.
The fix I've used is to try a different phone (that hasn't cached a previous version), or to make a new version at a different URL. Sounds crazy, but it worked for me!
We have also faced with this problem couple of times and possible reasons might be;
Due to the screen shots, did you upload your files to exact location "http://www.becomingapps.com/en/ota/" location? When you give this URL during enterprise export.
Second possible reason we have seen is mismatched App Id's.
In case you haven't solved your problem, I think you can't use a wild card in your ad hoc profile. It should have the full ...com.becomingapps.dilemma signature.
You also have to upload both the icons, but I'm assuming you did that since your screenshot shows a custom icon.
It's worth the effort to get this working, my customers love it.