i am creating a app on "appmysite" while it runs its build test an error message pops up saying build failed. "it seems your app build has encountered an issue. the certificate used to generate the uploaded provisioning profile does not match the uploaded certificate." I understand why its saying it because the uploaded certificate had to be uploaded as ".p12". The certificate in the provisioning profile is made of ".cert". I am using a apple mac book and a xenovo windows computer. Im simply trying to figure out how to put the ".p12" certificate into the provisioning profile? whenever i go to my developer account and try to create a new provisioning account with the new ".p12" certificate. The only options that pop up for me to select are only the certificates that are in ".cert" form. I've tried exporting through "key access" and they show up in my files but no way to transfer to my developer account to combine it with a provisioning account. Any help is greatly appreciated, this is literally the only thing keeping my app from being ready for submission to review. ive been stuck on this for 3 days.
I want to start by addressing this:
i am creating a app on "appmysite"
The Apple Developer Forums are primarily focused on Apple APIs, tools, and services. If you need help with your third-party tooling, I encourage you to seek that help via the support channel for those tools.
Having said that, I want to point you at some Apple docs that should give you a better model for how this stuff works:
- TN3125 Inside Code Signing: Provisioning Profiles explains what provisioning profiles do and how they’re structured.
- TN3161 Inside Code Signing: Certificates has a whole bunch of backstory about code-signing identities and their associated certificates.
because the uploaded certificate had to be uploaded as ".p12" [but the] certificate in the provisioning profile
This comment suggests you’ve misunderstood a key element of this process, namely the difference between a certificate and digital identity (a digital identity combines a certificate with a private key that matches the public key in that certificate). Your .p12 is a digital identity, whereas a provisioning profile contains a list of certificates.
TN3161 explains this distinction in detail. TN3125 explains how you can view the list of code-signing certificates that are authorised by the profile.
Finally, you tagged your thread with Developer ID, which is a specific type of code-signing identity used for distributing Mac apps outside of the App Store. Is that what you’re doing? Because most of the questions I see about this are from folks targeting iOS.
This matters because Developer ID signing identities are precious, as I explain in The Care and Feeding of Developer ID. If that’s the case then you need to be careful as to how you resolve this issue. However, if you’re targeting iOS, or any of its child platforms, then this isn’t a concern.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"