Create provisioning file for Push Notification - iphone

I want my App to support Push Notification, and I do as below:
Generate CSR file
Create an App ID and enable Push Notification
Create Development SSL Certificate for the App ID, using CSR file created in step 1
Create Provisioning file
The problem is, in step 4, I cannot select the certificate created in step 3. Is there anything wrong in my steps?
Thanks.

No you can't select push SSL Certificate while creating provisioning profile. Just select developer Or Distribution certificate.
Upload push SSL certificate in server that provide push service...ex: parse, arban airship. Its optional.

You can't select the SSL certificate just because you don't have to.
The provisioning profile is not related to the push certificate, but to the App ID, that's where you have set your app to use the APN service.
The SSL certificate must be uploaded on your server so it can be identified as your app server when making calls to Apple. You just need to download it, open it in your keychain and then usually export it and upload it on your server.
It's quite simple, just be sure to sign your app with a development provisioning profile when you are using a development push certificate on your server (making calls to apple sandbox server), and a distribution profile when you are using a production certificate.
If you are still getting problems take a look at this guide, it's from quickblox, but the part related to the Apple portal it's the same independently form the server or the service you are using to generate notification and it's really well explained.

follow this it might help you,
http://www.raywenderlich.com/3443/apple-push-notification-services-tutorial-part-12

I also followed all the tutorials mentioned above. I had the same issue with 'step 4'.
What I found out is that I cannot create a provisioning profile manually (using THE certificate). It automatically generates it for me once my Xcode 5 synchronizes with my AppId which was created by myself. So I would like to suggest that you wait a few minutes after you pressing the 'fix issue' button from the general tab. (BTW, I am new to IOS developer.)

Related

Do I need to update distribution certificate and provisioning profile right after generating and installing APNS production certificate?

I am working on one app and its uses the Apple push notification. For that there is one apple push services production certificate created by other user/previous developer. I am not able to contact my previous developer for the push certificate p12 along with its private key.
That is why I am trying to generate my own apple push production certificate from the developer site.
But my doubt is if I generate and install that new APNs Production certificate to my keychain , will it affect my existing provision profile and iOS distribution certificate(which is already installed in my keychain)?
Do I have to update them both after installing APNS production certificate ? If yes plz guide me with the procedure.

Implementing APN's, get valid signing identity not found when install development profile?

For APN's i'm following raywenderlich tutorial from here
i already have developer certificate installed in xcode, when i create AppId and configure it to push notification and create certificate(SSL) it adds a development certificate under certificate section..it's Ok.when i go to create provisioning profile it shows me only one certificate to choose(not newly created APN certificate). i created profile with that certificate but whenever i go to install it, it say "valid signing identity not found".
Please note that I've installed both iOS Development and APNs Development iOS certificates in xcode. I've searched similar question on stackoverfllow but still no luck.What I'm doing wrong?
I'm not sure what you are doing wrong. But here is the general procedure:
Go to developer.apple.com and login
Go to Certificates, Identifiers and profiles
Create a certificates for iOS app development and APNS. For creating a certificate you need to upload a CSR (use Keychain Access to do this) from your Mac. Once you upload the CSR from your Mac, download the App and APNS certificates to your machine - If you don't upload the CSR from your machine, you will get a valid signing identity not found error.
Points to remember:
When creating APNS certificate, chooose the appropriate App ID. By choosing wrong ID push notifications wont work.
When creating the provisioning profile, choose the App certificate you created in the above steps.
Thats the gist, you should be able to figure out things I missed by following on screen instructions.
I got the solution private key(.p12 file) was missing in keychain.

Valid Signing identity Not Found in Xcode

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

Push-Notification works on develpoment but not on production

So we have a problem with our app. We put push-notification in, and it works flawlessly in development. Then, once we got on the app store push no longer works. By looking at our server logs it looks like the the registration call is failing and not getting a device token.
Has anyone encountered this before?
Cheers,
Did you create a production push notification SSL certificate? This is most frequently the cause. Applications signed with a development provisioning profile will not work with a production push SSL cert and applications signed with a distribution provisioning profile will not work with a development push cert.
Also, you can create an ad-hoc distribution cert and use this to test your distribution provisioning profile. Since you can't run the build you send to Apple for distribution, I'd strongly encourage you to make an ad-hoc distribution build and confirm that push notifications work in that installation.

Not Receiving Push Notifications

previously i had configured my app id for development push notifications it was working fine.
But now i have changed my appid and i have followed the same procedure as stated in the apple docs and i have put newly generated .p12 file on the server side but i am not getting the push to my device now.
i have a doubt for an apple id i generate both development and production ssl certificates and in programme portal both environments shows green balls.
i have created development provision profile after doing as said above. in the sever side do i need to point to production ssl or development ssl for testing.
can anybody have any idea about this
It depends which server are you contacting.
If you are testing on the development side, you have to send requests to the sandbox (gateway.sandbox.push.apple.com) using the appropriate SSL certificate and the appropriated Device Token.
If you are on production/release mode, you have to use the correspondent info.
Another thing that you have to keep in mind is that, for each certificate you have to register your device for push notifications, and if you change the provisioning profile, you have to do everything again, because the Device Token will be different.
Cheers,
VFN
Make sure that the device which you are testing doesn't have both the development profile and the distribution profile. Only distribution (adhoc) profile must be there.