I am unable to launch my apps on an Android emulator anymore due to "Error generating final archive: Debug Certificate expired on 4/15/12 3:15 PM". How can I get another certificate? Why do I need one this was supposed to be free software?
Thank you in advance,
Maria
Delete your debug certificate under ~/.android/debug.keystore ;
The Eclipse plugin should then generate a new certificate when you next try to build a debug package. You may need to clean and then build to generate the certificate.
Related
I am using Unity to publish a game and I keep on getting this error when I upload:
You uploaded an APK or Android App Bundle signed with a certificate that is not yet valid. You need to sign your APK or Android App Bundle with a certificate that is currently valid.
I've checked several threads, and the problem they seem to target is the system time and date settings, but I double-checked that and it is correct.
What should I do?
You have to set the correct date and time of his/her system before generating keystore.
You can follow the following thread.
APK signed with a certificate that is not yet valid
The certificate you are signing your APK with has a validity start date past the current date.
Create a new certificate in the same or a new keystore, then update your gradle configuration to point to your newly created key and clean your project before re-creating a new APK (or App Bundle).
I already made iPhone application thanks to all certificates and so on.
Now, I'm installing a second mac to develop applicaions (the same applications) so :
I generated a Certification Signin Request (with keychain)
I didn't upload it but I downloaded the Distribution Certificate (that I generated before with the old computer), and install it (in keychain again)
I Downloaded the Distribution Provisioning profile
The last File , I installed it and in Organizer, the status of the file is "Valid Signing identity not found".
How can I fix that problem ?
This is common operations but I always have trouble with all those certificates :-)
Thanks
Export your existing certificate from your old machine to your new one. This will make you skip all other stuff to do and it's easy as 1,2,3.
When I upload my app to the App store I am facing the issue below:
Application failed codesign verification. The signature was invalid,
or it was not signed with an Apple submission certificate
I did all of the changes below:
cleaning project,
cleaning all,
deleting build directory,
deleting certificates + profiles
and reinstall distribution provisional profile and distribuction certificate
but still I am facing the same problem. What am I missing?
First, check that your certificate is correct/valid. To do this, log in to the iOS Provisioning Portal with your Apple developer account and create a new distribution certificate. Make sure that you specify that you want to store you app on the iOS App Store. Create a certificate for the App Store by clicking the App Store radio button - don't choose "Ad Hoc". After that, download and install the newly created provisioning certificate.
Check that you've done the following:
Set your code-signing identity in the XCode project to use the new provisioning certificate.
Used the certificate for Distribution profile, not just Developer.
Used the "Clean all targets" function in XCode.
Deleted any build folders from your application's directory tree in the Finder.
After that, build and run your application.
For a fuller explanation, see Apple's documentation about this.
For the iOS error "Application failed codesign verification", see Apple's complete list of potential causes at the following URL "How do I resolve the error: Application failed codesign verification?"
I had the same issue and tried all the solutions listed and then some. But it turned out that it was something so simple, I could kick myself! Set your Archive Build Configuration to Release. You can do this by going into PRODUCT -> EDIT SCHEME -> ARCHIVE -> BUILD CONFIGURATION -> SET TO RELEASE.
Good Luck!
I am using the Development Provisioning Assistant in the iPhone Developer Portal, but when I get to the part where it asks me to generate and upload my CSR, I try to upload it and it just gives me this error:
The CSR selected is invalid. Please check the file and try again.
Does anyone know what this means or what I can do about it?? Thanks!
Also make sure you use Safari for uploading.
I tried Chrome and it always failed. Then I switched to Safari and it worked with the same CSR.
Never mind, I figured it out... in case anyone else has the same problem, I fixed it by downloading the WWDR Intermediate Certificate before generating the CSR, which I forgot to do. slaps forehead
If you do not have the following menu item: "Keychain Access->Certificate Assistant->Request a Certificate from a Certificate Authority", then you need a new WWDR Intermediate Certificate. My menu item was originally similar, but had some extra text in the title. Downloading and installing a new certificate changed the menu item and allowed generation of a valid CSR. This was odd because my previous WWDR Intermediate Certificate appeared in my keychain as an unexpired certificate.
I logged a bug at bugreport.apple.com asking for a clearer error message and pointing back to this SO discussion. Edit: fyi.. apparently developer portal bugs should be logged by sending email to devprograms#apple.com instead of the "product" targeted bugreport website. I encourage folks that have wasted time on this issue to provide helpful feedback regarding the issue via email.
If you are not able to upload the CSR using launching assistant, try going to "Provisioning Portal -> Certificates". Upload your file there and click "submit" button at the bottom.
I had my certificate this way.
I had the same problem, and what fixed it for me was to repair my login keychain. Go to 'Keychain First Aid' in Keychain Access and you can verify/repair your config.
Second on the Chrome vs. Safari conflict and solution.
The instructions on the iOS Provisioning Portal -> Certificates -> "How-To" tab are exactly correct, but I have a repeatable failure on upload in Chrome, and instant success on Safari.
Versions:
OS: OS X Snow Leopard 10.6.6 64-bit
Chrome: 8.0.552.237
Safari: 5.0.3 (6533.19.4)
Did right the opposite: used Firefox instead of Safari and the button worked.
I had a similar problem.
When creating a CSR for enabling push notifications, I first had to deselect the current selected key in Keychain Access before selecting Request a Certificate from a Certificate Authority. That solved my problem
Make sure you have only "Request a Certificate from a Certificate Authority" and not something like "Request a Certificate from a Certificate Authority with key "
If under Keychain Access you only have the option for "Request a Certificate from a Certificate Authority with key" it will not work. This indicates you have not downloaded the "WWDR intermediate certificate". You can get it from the "Certificates" tab in the iPhone Provisioning Portal. Once its installed (double click it to install), the menu item will change to "Request a Certificate from a Certificate Authority" and it should work.
I have created a new iPhone application.I have two mach machines. I have created the certificate for running application in iPhone in one mac. Can I use the other mac for running the application in iPhone. But when I try to do so I get an error "Codesign error:Code signing is required for product type "Application" in SDK Device iPhone OS 3.1.2. Please some one help me.
Regards,
krishnan.
Have you transferred your credentials to the second Mac? They are stored in your keychain.
You may need to read up on how Code-signing works: http://en.wikipedia.org/wiki/Code_signing
Here's an overview:
Developer creates a Certificate via a Certificate Authority (CA)
This certificate is used to 'sign' the binary, providing 'proof' of who created it
Developer then uses the Certificate to sign the binary (this is the step you're missing on the second MAC)
This is handled via xcode, assuming you've followed the detailed steps on http://developer.apple.com/iphone
Clients using the binary can now verify the Certificate against a known CA to ensure the integrity of the build.
Also check that you are code signing on the target as well when you do the Archive build
Spent hours to figure this out. Actually you need to click on Project --> Build Settings --> click target --> code sign..
THIS IS not apparent