Hye,
I'm not sure what is the problem is, but whenever I want to submit my app, this will occur,
afterthat i've tried to revoke my certificate and quest it back, the status were "issued" . How can i solve this problem ? tq.
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)
Are you sure that you are using the distribution profile to sign your app for submission, and not the developer profile?
It's a common cause of this failure.
It could also be that you are using Xcode 4.5 or iOS6 (which are pre-release) and that is preventing submission.
In general - I find the Apple Technical Note on Code Signing Issues to be a great reference for solving such problems.
Related
Recently I deployed an app to the internal testing track in the play store. I had to fix the app package name to do so - my mistake naming it poorly in development - and it may be responsible for breaking something, mysteriously, in the Google OAuth system.
The error that Google displays is useless... It tells me I violated a policy! But not which one. It just says something about the redirect_uri.
I've been staring at the message "You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure." for days now, tearing my hair out. Apparently almost nobody else has seen this message, and it's not documented.
I had suspected I was using the wrong SHA1 certificate, but though it may have been incorrect, fixing it has not helped it.
Using the old (pre play store) package name in the cloud console works in dev, but not in production. Yes, I have a separate client id for the dev (signed with the default SHA1 for local dev) and a client id for the play store signed app... I'm pretty sure I've got it right now, though again, no details, I don't know. There's a reason I'm so obsessive about error codes and exceptions when I build software myself!
The only thing I've been able to do to change anything is by manually messing with the redirect_uri that expo-auth-session sends to Google, which sometimes causes a redirect_uri_mismatch... This indicates to me that the redirect_uri I'm using is a match? Meanwhile, redirect_uri_mismatch is a documented error code, but not redirect_uri.
What makes this more annoying is that apparently Google cloud OAuth config can take a long time to update, apparently up to a couple hours, but I have no idea when it's updated... So I can't tell if I'm testing against the propagated config changes? Huh??
I happen to believe that the lack of diagnostic info itself is a bug (how can you debug an opaque failure? An undocumented error?), But it seems like Google does not agree?
If it's helpful, I've been using Google OAuth for a year now for the web app part of this project... Never had this problem. I'm ready for launch. This is the only thing blocking. What am I to do?
There is a similar discussion about the Nest app, but that is attributable to the phase out of unsafe schemes: https://community.home-assistant.io/t/nest-authorization-error-error-400-invalid-request/399388
I'm in the process of integrating PayPal payments through Cybersource API. When I click on the button returned from the latter I got redirected to PayPal sandbox website and I'm shown the following error:
The certificate has expired. Please use a valid certificate.
I contacted Cybersouce support but they have not found anything wrong with my test account.
I know about recent changes in PayPal, but I don't know how relevant this is to my problem.
This error seems to pop up on various e-commerce sites when clients complain about not being able to pay with PayPal. Unfortunately none of those places mentioned what was the fix.
Can anyone at least point me to the direction I should be looking for a solution? Which certificate this error mentions? Is that the API certificate for SOAP integrations as mentioned here?
In my case I was referring to the expired certificates Cert ID, You need to consider new Cert ID after uploading new certificate to Paypal.
This link will walk you through the process.
I've developed application which communicates with my own server over HTTPS. And I use .p12 certificate for mutual authorization. The problem is that after I send first request on server I receive OSX's dialog message:
I know that need to make code sign but:
Can I make some workaround/hack/trick to prevent it? Please note that my app is not going to go on Mac Store. So I could use any private API.
If we can't prevent this dialog then what should I do:
1. Code sign my application via Mac Developer Program?
2. Or make trusted my p12 certificate?
If need to make some of these items above please provide a quote as proof from Apple's documentation.
I use OSX 10.8 an later.
Code signing your application is the most straightforward way to avoid this dialog. When importing the certificate and private key your signed application and future versions that match its designated requirement will be given access to the key for all purposes. See Mac OS X Code Signing In Depth and the Code Signing Guide for more information.
On your development systems that have already imported the key into the keychain you may see the authorization prompt one additional time, on systems that do not yet have the key in the keychain the prompt shouldn't appear at all.
I'm at the point where I'm ready to submit an app - an Apple doesn't elaborate much on how to sign and submit apps. I have both the WWDRCA certificate and one I created but am at a loss on where to put them.. do I add them via drag n' drop into XCode? Why do I need the WWDRCA? Anyone have any info on this? Would be GREATLY appreciated
First, make sure you have correctly installed the Installer, Developer and WWDR certs in your Keychain.
In Xcode, edit your target build settings and under 'Code signing entity' and select your Developer certificate. Then build your app using 'Build and Archive'. Finally, open Organizer (via Window menu) to verify and submit your app.
At least, that's the theory. I agree that it's tricky. The Apple Developer Forums have several instructive postings about the potential pitfalls. Good luck!
Edit: Dang, I missed that it's about the Mac App Store, my post is about iOS... For the Mac App Store, there's also a document from Apple and a checklist with links. That checklist seems like a good starting point for all the relevant information.
Original iOS related post:
If you log in to the Provisioning Portal, Apple explains in detail how to get and use a certificate (now even with videos). Right when you login to the portal, see the right column. Or click on the "Certificates" link on the left and then on the "How to" tab. It's step-by-step guide with screenshots. Also, see the "Provisioning" section in the left meny, again click the "How to" tab. For submitting, see the "Distribution" section in the menu on the left. If you still have specific question after reading/watching that material, go ahead and ask.
You need the WWDR CA certificate so that your keychain and Xcode can actually validate your certificate. Certificates are signed by other certificates and form a chain of trust. But there has to be a start, and that is the CA certificate for which you first explicitly state "Yes, I trust this certificate" and thus all certificates that were signed by it.
This is also how your browser works with HTTPS: your browser comes with a bunch of CA certificates that it trusts by default, for example the CA certificate from Verisign. And if your browser then sees a certificate that was signed by Verisign it knows it can trust that website since it already trusts the Verisign CA.
"Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)”
I get this error when trying to upload my app through the Application Loader.
Any ideas whats wrong and how I can sort it?
Adam
You can check your configuration in this iPhone development forum topic
I've seen this error pop-up due to XCode 4.x incorrectly handling schemes whose names contain spaces