I ve deployed the application with the keystore with certificated added.
I generated the keystore and cert using the keytool eclipse plugin.
i installed
Now the issue is upon installing it on device there is an error message like this "Certificate not on phone or sim".
Then installed the cert on device as instructed here (http://www.nokia.com/in-en/support/troubleshooting/?action=singleFAQ&caseid=FA139228_en_US).
Still i'm getting the same error mesg as "Certificate not on phone or sim".
I use a verysign certificate on Netbeans, and always works. Can you try to put on teh security option from the preferences menu of a project.
Related
i getting in started with the google drive api, and i'm following the tutorial at https://developers.google.com/drive/quickstart-android. I need to generate a fingerprint sha1, but i see in the preferences of eclipse (preferences > android > build) an existing fingerprint sha1, associated with my project. So i have some question in my mind:
Eclipse generate fingerprint sha1 for each project?
What's the function(s) of fingerprint sha1? Only for certification that i write the app?
Eclipse, by default, generates a key for debugging purposes and it's located on ~/.android/debug.keystore. Each Android app needs to be signed with a certificate to confirm authorship. Eclipse generates a keystore per user and signs the app's with the default cert from that keystore during development.
Actually i developed an app using my own developer certificates and provisioning profile.
Now i need to publish it on my client developer account and my client sent his distribution certificate along with provisioning .And I have installed the certificate and then i drag the provisioning profile to xcode, and i have got error message like "Valid signing identity not found"
Please assits me.
Change code sign in project settings.
You need the private keys that were used to sign the certificate. If you don't have them
anymore you can generate a new signing request.
You need p12 file from your client to use its developer certificate and provisioning profile.When your client provide you that p12 file than double click that file and its run perfectly.
And for geting p12 file ,select the cert, and open the arrow to also select the private key and export them together as a .p12 file from Keychain Access.
There are several ways to solve this issue.
The first one is, to export your developer certificate including the associated key from your keychain and importing it on your client machine.
The other way would be (If your client machine would use another apple dev account) to go through those steps listed here Apple Certification & Provisioning
I would recommend to delete the old certificates from xcode, sometimes xcode might lag otherwise
I have developed ios application and generated ipa file and installed it on my ipad using provisioning profile it works fine. now i need to install same ipa file from another mac and another iphone device. i have used existing certificates in organizer but it says invalid code signing. how to solve this issue?
certificates are system specific. u need to export your certificate from your system to .p12 or .cer file from your keychain then only it can be used upon installation of that certificate on some other mac system.
with certificate, you would also need the provisioning profile with which you were compiling the build earlier using that certificate.
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.
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.