问题
I made the IOS application using PhoneGap Build its working fine, but now I wanted to add (APNS) notification for that I made iPhone Developer Certificate from Mac for push notification and p12 file, provisioning profile. I followed all the steps mentioned Here.
Still it shows No iPhone Developer/Distribution identity found on your certificate Error while building my application.
Is this the right way what I am doing or any other solutions to do it let mi know.

回答1:
Just spent an hour on this - evan is correct. most likely you exported only your private key and did not select both the certificate and the private key for export. both of them result in a .p12 file.
回答2:
- Go to Keychain Access --> My Certificates
- Select the Certificate you plan to use and cross-check by expanding it (Select the drop-down icon on the left) to verify the private key.
- Right click and export it.
- Make sure that the provisioning profile you plan to use is signed with the certificate which you are exporting
Hope this helps.
回答3:
ok finally I got my solution after a long time.
Just follow these steps.
And while you are building your application through Phonegap Build use Provisioning profile which you made using above steps.
.P12
- Use .p12 file of your any development or production certificate depend on situation if you are doing for development then use any development certificate associated .p12 file and if you are doing for production then use any production certificate associated .p12 file.
If you are using .p12 file of certificate you have made it using these steps then you will get above error while building the app.
回答4:
I had exactly the same problem - the solution was as Mahendra says, that you must select BOTH the certificate and the private key, i.e. using cmd and clicking them both, when exporting from Keychain (and then make sure that you select the same certificate in the provisioning profile of course).
来源:https://stackoverflow.com/questions/18531812/no-iphone-developer-distribution-identity-found-on-your-certificate-error