Suddenly, when running a build of my Windows Store app I got the error.
error APPX0108: The certificate specified has expired. For more information about
renewing certificates, see
http://go.microsoft.com/fwlink/?LinkID=241478
There is a link to the Renewing a certificate page but it's just a circular reference.
The information was there - just buried at the bottom of the page:
Open the .appxmanifest file in Visual Studio (app manifest designer view)
On the Packaging tab in the
Click Choose Certificate
In the dropdown, select Create test certificate...
This blog post recommends you do not set a password
Agree to replace the certificate
You have to create a new certificate:
Open the Package.appxmanifest
Select the Packaging tab
Click Choose Certificate
Click Create
Enter your existing publisher name
A password
Agree to replace the certificate
Then you can update your microsoft store app
Related
When I refresh my Organizer I get the
No iOS Development certificate was found. However, there is already a certificate request pending. An Agent or Admin must approve this request before you can download your certificate.
message.
I login to my devloper account and check out the certificate - its seems fine (ie not expired). I then check out the pending section - but there isnt any there to approve.
I then download the Certificate that is associated with my apps provision profile, install it on KeyChain by double clicking it and try to refresh Organizer again. But still get the same error.
Am I missing a step here at all? What am I doing wrong?
Just revoke your certificate from your developer account then create certificate again.
This is because, present certificate is associate with other system's CSR(CertificateSigningRequest). So either get export certificate(.p12) of present certificate (just install certificate from which it was created, right click and then export will give you cer.p12 and it will run on you other system ) or just revoke and create againg.
Do you have access into itunesconnect.apple.com ?
It seems, your certificate is Entering in Corporation Team. And Admin of corporation must enter to developer.apple.com and click Approve on your certificate request.
And you can download your certificate and install him. Provision file it seems is exist.
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 an active distribution certificate.
But when I go to create Distribution Provisioning profile I see "Please create a Distribution Certificate" in Distribution Certificate field:
But when I go to create Development Provisioning Profile The Certificate field contain an active Development certificate.
When I go to this link "Please create a Distribution Certificate", I see the following screen, but after that, how to submit the certificate, the page just reloaded and nothing happens.
Please, help me! Thank you!
hey when you go to create development profile have you browse the certificate ( generated by key chain access) by clicking the browse file button at lower left corner after browsing then you click the submit button then you get the distribution certificate.
follow the steps given below link:
http://mobiforge.com/developing/story/deploying-iphone-apps-real-devices
Best approach would be to remove every certificate / profile which has to do with "developer" or "Xcode" in the Keychain Access. Then, join the provisioning portal and do all the steps on the left from up to down.
Download the certificate from the apple portal, create your own certificate and upload this one on the site you are on in your question. This should do the trick.
I also had this problem, because there was more than one developer profile installed on my laptop which crashed everything.
I am about to upload an app to iTunes Connect. I am not Team Agent, nor does it seem the Team Agent can make me a Team Agent. So he logged onto Member Center and downloaded a Distribution Certificate, which is in my Keychain along with the WWDR Certificate.
The bundle identifier is set to se."companyname"."appname".
When I set the Code signing identity to Distribution, it says no profiles match. Can only the Team Agent build the final apps for upload? How do I make XCode "use the right set of profiles"?
Any idea on how to get past this last hurdle? :)
Edit: can the Team Agent log onto Member Center and create a provisioning profile for the app, will that solve everything?
Answer: See Paul Peeleen's answer, I decided to add this additional information (too long for comment).
Paul, I'm going to mark yours as the correct answer, because it set me on the correct track... certificates are for the keychain (which is usually linked to a computer, or rather, a computer user's login, I guess).
A quite separate distribution profile must be created for the app - modifying an existing Development certificate to include the Team Agent only lets him develop. The little 'a-ha' or perhaps 'd'oh' moment was that it has to be created in the Provision section with Distribution tab selected (in the provisioning portal).
After that, in the Target Info/Build tab you just use the default automatic profile selector (dev/distro) and it's found automatically.
I also temporarily tried adding the 'gibberish' (f.ex. JX567ERNB.) before the se.companyname.appname for the Bundle Identifier, but the automatic profile selector told me that it shouldn't be there, I removed it and it worked!
The profiles are what enable the projects to use certificates in the Keychain, I guess.
"iPhone distribution no profiles match" is one of the most annoying issue that I have ever had with app development.
This is how I sorted it out:
In Developer under iOS Provisioning Portal I needed to generate 4 certificates and download the WWDR intermediate certificate to be able to submit my app to the App Store:
Under Developer Certificate section (link) generate a Developer Certificate. Also Make sure that you have the WWDR intermediate certificate installed, if in doubt download it from there.
Under Developer Certificate section (link) generate a Distribution Certificate (This is not that will show up in Xcode!)
Under Provisioning section (link) generate a Development Provisioning profile certificate
Under Provisioning section (link) generate a Distribution Provisioning profile. THIS WILL SHOW UP IN XCODE AS A DISTRIBUTION CERTIFICATE!
After that I was able to select the iPhone distribution profile generated at 4. Also make sure that your target settings are correct as they overwrite the project settings.
Your active provisioning profiles are listed under "Xcode/Organizer/Library/Provisioning Profiles"
I hope it helps
UPDATE: Some distribution provisioning profiles often just "disappear" from my list. So I have to download and install (just double click) them again from https://developer.apple.com/ios/manage/provisioningprofiles/viewDistributionProfiles.action not a big deal, but annoying.
I checked this with my accounts and it seems that only the team agent can create the stuff needed for AppStore or AdHoc releases.
IF you have the correct provisioning profile installed, and both your project settings and target setting for the "release" build are set to the correct provisioning profile. + that you have the correct certificates installed for that computer... you can build the release.
I am unsure if only the Team Agent can upload these build, but otherwise you can package the release as a zip file (which you should anyways) and send it off the the team agent. The Team agent can then use the Application Loader to upload the application.
Also dont forget If you deleted all your certificates and keys in Keychain and you plan on regenerating those certificates make sure you change your certificate preferences in Keychain for Online Certificate Status Protocol to Off and Certificate Revocation List to Off, for some resaon this important step is the only way it worked for me.
Another reason developer profiles are missing
While in organizer under Library > Provisioning Profiles...
On my computer, if I hit Refresh, all the Distribution profiles are removed!!!
No big deal, just go back to your provisioning portal and go to Provisioning > Distribution and download the appropriate distribution profiles and your good to go! :)
Instructions right from apple... Follow them EXACT
https://developer.apple.com/ios/manage/certificates/team/howto.action
To request an iOS Development Certificate, you first need to generate
a Certificate Signing Request (CSR) utilizing the Keychain Access
application in Mac OS X Leopard. The creation of a CSR will prompt
Keychain Access to simultaneously generate your public and private key
pair establishing your iOS Developer identity. Your private key is
stored in the login Keychain by default and can be viewed in the
Keychain Access application under the ‘Keys’ category. To generate a
CSR:
In your Applications folder, open the Utilities folder and launch
Keychain Access. In the Preferences menu, set Online Certificate
Status Protocol (OSCP) and Certificate Revocation List (CRL) to “Off”.
Choose Keychain Access -> Certificate Assistant -> Request a
Certificate from a Certificate Authority. Note: If you have a
noncompliant private key highlighted in the Keychain during this
process, the resulting Certificate Request will not be accepted by the
Provisioning Portal. Confirm that you are selecting “Request a
Certificate From a Certificate Authority...” and not selecting
“Request a Certificate From a Certificate Authority with …”
In the User Email Address field, enter your email address. Please
ensure that the email address entered matches the information that was
submitted when you registered as an iOS Developer. In the Common Name
field enter your name. Please ensure that the name entered matches the
information that was submitted when you registered as an iOS
Developer. No CA (Certificate Authority) Email Address is required.
The ‘Required’ message will be removed after completing the following
step. Select the ‘Saved to Disk’ radio button and if prompted, select
‘Let me specify key pair information’ and click ‘Continue’.
If ‘Let me specify key pair’ was selected, specify a file name and
click ‘Save’. In the following screen select ‘2048 bits’ for the Key
Size and ‘RSA’ for the Algorithm. Click ‘Continue’.
The Certificate Assistant will create a CSR file on your desktop.
I battled the problem all day too. Tried Tons of things.
I downloaded the distribution provisioning profile. OK
Double Click. Into Keychain it goes (like magic) OK
Build. NOPE. Not Signed
Check - it is not the Team Provisioning Cert that you are looking for it is the plain looking one that cannot be installed on devices.
If it is not there you did not copy it to YOUR library/MobileDevice/Provisioning Profiles folder. (just like I didn't)
Make sure that the case of your bundle identifier in the provisioning profile and your info.plist are the same.
I just had this problem, and resolved it finally when I saw that Xcode would not even let me manually select my distribution profile, saying 'profile doesn't match bundle identifier myappname'
When a took a close look, I saw that the bundle name had the app name capitalized, and the provisioning profile had the appname in all lowercase.
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.