Push ssl certificate missing private key in keychain

Question

I am updating some applications in the application store to integrate Push notification, and I have problems with push ssl certificates.

When I created non-push applications, I used the wildcard App ID, for example myradio.* , And then I created a new explicit application identifier corresponding to the app package identifier, for example myradio.radioname .

I configured push with certificates, but haven’t used it at the moment, and now that I need to use these application identifiers, when I install SSL certificates for development and production, they lack a private key in Keychain. Maybe because I revoked my development certificate. But for some applications, everything works fine.

It is not possible to create another application identifier with the same suffix, and it is impossible to use an existing one, so you know how to update my applications?

Answer 1

Is it possible to simply change the package identifier inside the application and then create a new application identifier and provisioning profiles with a new identifier? For example, for example, your current package identifier is com.myradio.radioname, why not just change it to com.radio.radioname. I hope I understand what you are asking. I personally just use Parse.com push notifications , which is very easy to configure, I suggest you study it.