Apple Push Services created instead of Apple Production iOS Push Services

B

4

33

I'm trying to create a certificate for Production iOS Push Services. Instead I get an Apple Push Services. How can I create a dedicated Apple Production iOS Push Services certificate?

The top certificate is what I used to get. The bottom one is what I now get.

I use Pusher application to test my push notifications certificate and it cannot read the p12 of the new Apple Push Services.

Basilbasilar answered 23/12, 2015 at 8:16 Comment(7)

Do you need APNS to send push notification right? – Shavian 23/12, 2015 at 8:38

Do you need. certificate for code sign or you are looking for SSL certificate ex. .p12,pem ? – F 23/12, 2015 at 8:41

SSL - the one that my server uses to send the push notifications – Basilbasilar 23/12, 2015 at 8:42

Same problem for me, All of my previous certificates are working, But with new certificates I'm getting error like "You have selected the Production server, yet your Certificate does not appear to be the Production certificate! Please check to ensure you have the correct certificate!" (Server team is using Pushsharp to send notification). – Duhamel 23/12, 2015 at 9:23

@godmoney have you found the solution to this problem? I'm having a similar problem but I use PubNub push service. – Polanco 28/12, 2015 at 12:24

Not yet unfortunatly – Basilbasilar 30/12, 2015 at 10:6

@godmonkey i too facing same issue. Have you found a solution? – Hypostasize 14/1, 2016 at 23:35

D

42

Apple have changed the name of the certificate that is issued. You can now use the same certificate for both development and production. While you can still request a development only certificate you can no longer request a production only certificate.

Since the purpose of the certificate is no longer production only Apple has changed the common name to Apple Push Services. The functionality of the certificate is not affected.

Unfortunately services that validate the CN of the certificate may reject this new name. There is nothing you can do about this until the service updates its verification code. For example, Parse.com had this issue a few days ago but their verification code has now been updated and they will now accept the new certificate name.

Disunion answered 23/12, 2015 at 9:9 Comment(10)

Same problem for me, All of my previous certificates are working, But with new certificates I'm getting error like "You have selected the Production server, yet your Certificate does not appear to be the Production certificate! Please check to ensure you have the correct certificate!" (Server team is using Pushsharp to send notification).. – Duhamel 23/12, 2015 at 9:22

what's "CN"? sorry maybe I have lost some knowledge. – Winnick 30/12, 2015 at 9:54

The common name that is embedded in the certificate. – Disunion 30/12, 2015 at 10:13

@sivakrishna, have you find a solution for PushSharp? – Junna 4/1, 2016 at 8:7

@Junna No, my service team is unable to edit/change any thing on those classes, for your reference github.com/Redth/PushSharp/pull/586 – Duhamel 4/1, 2016 at 10:2

@sivakrishna, alright, thanks! Yes, I have seen your comments on that thread as well. – Junna 4/1, 2016 at 10:13

@Junna It seems they have to change the files..., let me know if you find any solution... – Duhamel 4/1, 2016 at 10:15

@sivakrishna, no, not yet. I'm looking for a solution from last year :D – Junna 4/1, 2016 at 10:16

And it is called Apple Push Notification service SSL (Sandbox & Production) – Apprehend 4/4, 2017 at 14:6

Then I could delete the certificate type APNs Development iOS or is it still required? – Unclose 4/9, 2017 at 13:6

F

9

Apple Change Apple Production IOS Push Services cert name to Apple Push Services if you used pushsharp , you need go to github https://github.com/v-tsymbalistyi/PushSharp download zip and used visual studio recombile because the code change if (production && !subjectName.Contains("Apple Production IOS Push Services") && !subjectName.Contains("Apple Push Services")) throw new ArgumentException("You have selected the Production server, yet your Certificate does not appear to be the Production certificate! Please check to ensure you have the correct certificate!");

            if (!production && !subjectName.Contains("Apple Development IOS Push Services") && !subjectName.Contains("Pass Type ID"))
                    throw new ArgumentException("You have selected the Development/Sandbox (Not production) server, yet your Certificate does not appear to be the Development/Sandbox certificate!  Please check to ensure you have the correct certificate!");

and you just copy PushSharp.Apple.dll to server then everything OK

Fadil answered 7/1, 2016 at 6:19 Comment(4)

Additionally, try the 3.0 series of PushSharp where this is fixed and generally works better anyway :) – Mcdermott 11/1, 2016 at 13:24

Do we need to remove line which throws exception? – Execute 12/2, 2016 at 15:30

@Redth, 3.0 is still in beta, Also getting error as "Unable to find version '3.0.0-beta29' of package 'PushSharp'." while trying to install – Execute 12/2, 2016 at 15:30

@Mcdermott can you please check that: #35603163 – Boothman 24/2, 2016 at 16:46

S

4

Login Apple Developer Account.
In Member Center -> click Certificates, Identifiers & Profiles
Choose IOS apps
In Certificates -> click add new(+)
There you can see Apple Push Notification service SSL (Sandbox) [for development] and Apple Push Notification service SSL (Sandbox & Production)
To click on continue , choose Appid(bundle id)
Need to continue. This have the demo to generate csr
Add CSR file
Then it generate APNs. Put the name for it.

Note: You can generate APNS for Development through Apple Push Notification service SSL and Production for Apple Push Notification service SSL (Sandbox & Production).

Shavian answered 23/12, 2015 at 8:43 Comment(3)

When I generate Apple Push Notification service SSL (Sandbox & Production) then Apple Push Services is created instead of Apple Production iOS Push Services – Basilbasilar 23/12, 2015 at 8:49

Can you send the screen shot of it. I think both are same . you don't worry of it. That is production APNS. i will attach the screenshot of mine. – Shavian 23/12, 2015 at 8:51

Yes - I see something else. Added a screenshot to my question. – Basilbasilar 23/12, 2015 at 8:55

F

1

Then click on you App Id in developer account App ID -> Edit -> you will get development and production ssl certificate mode.

Then upload your CSR file=> download aps_production.cer

Then use This link to create PEM file (Which used on server)

There is one simplepush.php file you can test from your mac cmd.

Hope this will help.

F answered 23/12, 2015 at 8:45 Comment(3)

When I generate Apple Push Notification service SSL (Sandbox & Production) then Apple Push Services is created instead of Apple Production iOS Push Services – Basilbasilar 23/12, 2015 at 8:49

Yes you are doing right. Now right click on Apple Production iOS Push Services export you will get private key as a p12 file. use this for create certificate refer tutorial – F 23/12, 2015 at 8:58

I use Pusher application to test my push notifications certificate and it cannot read the p12 of the new Apple Push Services. I uses only the p12. – Basilbasilar 23/12, 2015 at 9:1

Recommended topics

Hot tags