Would it be possible to change the Safari Developer certificate (created with a different email) of an extension and still have it auto update to all users?
You probably have to get a new certificate, as you won't be able to change any info on a digital certificate.
Related
I have keystore however I forget password of it so I cant get apk in react-native.
Is there a way to find password of keystore file ?
You can apply bruteforce, dictionary, mixed strategies with software tools like Android Keystore Password Recovery: anyway it will require time.
In the event that you are in the need of updating an app in Play store, consider also asking for an upload key reset by Google, by providing a new upload_certificate.pem from fresh keystore to them.
I am trying to implement APNS for my App and am hitting a wall while trying to generate a provisioning profile. I followed the instructions to create an APP id and was able to generate an SSL certificate for my App (the type is shown to be APNs development IOS). However, when I try to generate a provisioning profile, following the screen where I choose the AppID of my app, I do not see the SSL certificate I generate for this app. In the certificates list, I only see a certificate of type 'IOS development' that was created previously. I have been stuck on this issue for a while. Can someone please help?
Thanks
I resolved my own query. we need to add iOS development certificate while creating profile for APNS. You should have the p12 of that iOS development certificate.
I have developed an iOS app for my corporation. We distribute it via AirWatch. Some of the certs are going to expire soon and it is SO confusing to try to figure out what to do. I have googled and it seems every page has different information. I would really love it if someone could point me in the correct direction.
I have an "iOS Development" cert with my name on it. It appears that I cannot renew it, only revoke or download. Some pages said if I download it again it gets updated, some say I need to create a new cert. Which one is it, and do I do this in Xcode or on the portal?
I have an "APNs Production iOS" cert with my company's id on it(the reverse dns thing, like "com.apple.mobile". It is also due soon. How do I renew, and where do I renew it, in Xcode or the portal.
We do not use Apple Push Notifications in the app, but I am under the impression that you still need this as it is the way Apple securely identifies your app. Is this true?
I have a "iOS Provisioning Profile" that will also expire. Same questions. Can I just edit it to renew it? Do I do this in Xcode or Portal.
Thank in advance.
Yes, you will need to renew your profiles (all that you are using for development or distribution. Then, you will need to re-build any apps that were built with the old profiles. Otherwise, no one will be able to install the app that was build with the expired profile. Basically, any apps built and distributed with an enterprise distribution profile will need to be re-built at least once a year.
Edit: more details on how to generate a new certificate.
Just go the the ios developer portal, and go to the area on the right for Certificates, Identifiers, and Profiles on the right. Go to the Certificates area, and click the + icon to generate a new certificate. Follow the instructions there for generating the new cert. Once you have your new cert, go to the profiles section, and you will need to re-generate your profiles with the new cert. For each profile, click the edit button, change the certificate dropdown to your new certificate, and then click the Generate button. Download the new profile, and use it to re-build your apps.
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.