I'm trying to generate an Apple Push Notification service SSL Certificate - here's a screen-grab:
(source: 818kimball.com)
(blurred certificate name for privacy purposes)
but after hanging at that screen for 2 minutes, I then keep getting this error:
(source: 818kimball.com)
I'm doing everything right, I checked and re-did all my steps, several times, verified it all using multiple sources (like http://mobiforge.com/developing/story/programming-apple-push-notification-services) - but this error keeps popping up.
Anyone have any idea what's going on or how to solve it?
And in the error, where it says "or try using the Provisioning Portal" - anyone know what specifically they're talking about? I mean I know where the provisioning profile is, I poked around in there - but what specifically am I supposed to click or do there?
Any help would be greatly appreciated.
This have happened to me sometime. I think i got it solved by using another apple id(since my company had another one). But that may not be necessary. Try doing it after sometime, clearing all your browser cache. It should work, if what you are doing is correct
Related
I started a developing an app back in ~2009. It seems somehow there are 7 copies of the app I started developing. I'd love to delete all of them, but none of the 7 copies will load a dashboard page... you know... the dashboard page with the "delete" button. How should I proceed to remove these apps?
I get an HTTP500 from Facebook's servers via each link.
As suggested I reported this to Facebook as a bug mid Monday. I gave them my personal info so they could see my exact data. They were able to reproduce the "bug" and confirmed to me that something was wrong right away (within hours). Just now (mid Friday) I got a message stating essentially, "yeah, some system somewhere messed up when creating your apps, so they got made in a broken state. We manually deleted them for you." So while there may or may not still be a bug out there, my problem was solved in ~4 working days by reporting it directly as a bug.
Anyone else getting this error when trying to download an app from the new Apple Mac App Store?
INSTALL_ERROR_DISTRIBUTION_SIGNED_BY_APPLE
I just ran into this problem while trying to update an application, but my problem was not an unsynchronized clock (ntpdate -q time.apple.com showed a maximum offset of 0.022479).
I found a hint in an a thread on one of Apple’s discussion forums that the problem might be related to certificate status checking settings. Modifications in this area resolved the problem for me. In the Keychain Access application, after selecting the Keychain Access menu > Preferences… menu item, and switching to the Certificates tab (close this preferences window when done making any changes), I ended up changing both my OCSP and CRL settings from “Require if Cert Indicates” (which seemed like a useful, “strict” setting to me), to “Best Attempt” (the Priority remained “Require Both”).
It seems that the “Require if Cert Indicates” and “Require for All Certs” options are normally grayed-out (I originally set them back on a machine running Tiger, which was migrated to this Snow Leopard machine). I found that you can hold down Option while clicking on the popup button (a.k.a drop-down list) to enable and select these options though. I may go back and try to determine which setting (OSCP or CRL) was strictly necessary.
I got the same error because my OS time/date was not correct.
I tried repairing disk permissions to try and get rid of a 100013 error I was getting on a development certificate, left the computer alone for the weekend. When I came back and tried to build my program I got an error :
com.apple.tools.product-pkg-utility: error reading property list '/Users/Kevin/Desktop/iProspectLite/Entitlement.plist' - property list has no object.
How do I fix this? the documentation provided by other people and apple is overly confusing for a novice developer such as myself.
The best documentation is inside the developers portal - right where you create the provisioning profile (a step-by-step explanation).
I have used it few times in the beginning until I got used to this process...
I'm going crazy! I'm trying to upload the binary of my first application but I have always the same error!
"The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate."
I did everything, EVERYTHING!!
I created the request for the certificate, used it for both developer and distribution certificate, created the provisioning profile (12 times!!!) always cleaning my keychain and my Xcode deleting the old certificates and profiles..
I reboot the machine, reboot Xcode, the log is correct, but... I can't upload my app!!!!
Checked if my iPhone is connected (i tried with iPhone disconneted too).
I checked the certificate in both my project settings "Distribuition" Configuration (duplicate of "Release" configuration) and in my target settings.
Reveal in finder, compress the app and sent the zip...
I tried with Application Loader and iTunes connect online..
but nothing! NOTHING!!
I've spent 8 hours! And again i can't have my app uploaded!!!
I'm really going crazy!
Can anyone help me pleeease?
Thx!
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 diagnostics. Good luck!
Been there - done that.
Make sure your certificate is in the "login" keychain, and that that i the default keychain (highlighted bold) in Keychain Access
Make sure you have both the private and public keys for your certificates and that they are valid. You will also need the Apple Worldwide Developer Relations Cert Authority installed.
I assume you have dragged the profile into xcode - easiest to drop them onto the xcode icon on the dock.
Make sure as Paul says, that the bundle identifiers all match up
You say you checked the certificate in the distribution configuration. Its not the certificate you need to concentrate on but the provisioning profile.
Select your Release config top left, click on the project under groups & files and do cmd I. Select build tab and then pick distribution in the top left. Then look at the Code Signing Identity. Pull down the dropdown list and make sure you have the right application identifier, the right profile and the right certificate. Don't use the Automatic Profile Selector.
Hope one of those steps helps!
I was getting the same error when I tried to submit a version update from the Organizer. What solved my issue was using the Application Loader found in the directory /Developer/Applications/Utilities. You'll need to compress your .app file and send the corresponding .zip file. I used this for my initial submission as well, I just thought I'd try the new way. What a pain! Go with Application Loader.
Best solution:
Revoke Distribution Certificate
Create new AppStore provisioning profile
This solved my problem. Spent 4hrs+ :( :)
I just had this problem. I resolved it, after hair-pulling, by going back into Keychain Access one more time and discovering the "Show Expired Certificates" menu item. When I did that, one more expired cert of the kind I had (so far, unsuccessfully) replaced showed up! I had deleted a couple of expired certs already, but this menu item caused another to show up, and after deleting it, my upload worked. I was previously aware that expired certs can get in the way of valid ones, and I STILL wasted a lot of time. Hopefully, this helps some people.
iTunes connect keeps rejecting my binary for an application update and it's driving me mad. Usually I can figure it out but I've tried everything I can think of. Maybe someone can lend a hand :)
The error I'm getting is:
The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.
I am uploading an updated version of my app to the store. The current version is 1.0, this new one is 3.0. Here's what I've tried:
Zipped the app bundle with the
command line (I've heard the Finder
zip utility can be bad sometimes)
Checked my app is signed properly
with $> codesign -vv myApp (says
"Valid on disk)
Checked in the build
log for the correct provisioning junk
to be there
Made sure in my
Info.plist file the CFBundleVersion
and CFShortBundleVersion are
incremented from my current version
That's what I can think of to check so far, and everything looks good as far as I can tell.
Now I've read somewhere in the Portal that says you must sign updates with the same Distribution Cert as before, and I am (I think). However I have to sign with a new provisioning profile because the old one I used for App Store has expired (or something, I don't know it just won't work).
Things to know about my situation
This update is actually a complete re-write from a new template, BUT I've made sure I'm using the exact same App ID (wildcard) and bundle indentifier) so that shouldn't be a problem.
Also, I've switched machines since I last submitted to the App Store but I remembered to export everything (I think) from my old machine. I still have the old one here, with all the same data on it, if that's helpful. I don't think I've forgotten anything).
Thanks in advance for any help :)
Update
So I've decided to try uploading with the Application Loader to see if it will give me any new errors, and it has, it spewed this out into the console. Perhaps someone can find something meaningful there.
Also of note, the Portal Guide says Updates must be signed with the original Distribution Provisioning profile as was used to sign the original app. I've tried using that old one, but Xcode won't let me select it, as there's "No matching key pair" or whatever. Is there a way to remedy this? According to Keychain I've got my Distribution Cert and its private key, it all looks valid. I've made sure to try Repairing the Keychain in case, but no change.
This is always the fun part, isn't it?
Assuming you've double and triple checked the usual stuff (using the right cert, compiling for device, have a proper icon file, app ID, etc.)
One obscure reason I've run into was roughly the same as the one outlined here:
http://discussions.apple.com/message.jspa?messageID=9167082#9167082
To sum up, my project.pbxproj file somehow ended up with two different entries for PROVISIONING_PROFILE (even though the XCode interface only showed one). My file looked a bit different from the one posted in that discussion, but removing the extra entry fixed the problem for me.
It's simple! Just let Finder zip it.