PARSE Push notifications Production help needed

Get Started | Login

Discussion Forums > Plugins, Customizing, Source Code

Replies: 6 Views: 197

LeonG Apple Fan Posts: 694 Reg: Nov 08, 2011 Hamburg 17,740	confirm \| cancel 10/24/12 05:38 AM (13 years ago) PARSE Push notifications Production help needed Hi there, managed to get the push notifications running with Parse.com but now I need some expert help with the production side. As I understood, I just needed to exchange the certificate from development to production and upload this in the Parse Control Panel. Did that and still get a green mark in the test area. My Ad-Hoc signed iphones do get the push notifications, but if somebody downloads the app from the App Store, they dont get the message: "do you accept push notifications blabla.." As in Parse docs it says that in production status, both ad-hoc and app store production profiles should get the messages. So long post... Can anybody help me out? Title Comments Hi there, managed to get the push notifications running with Parse.com but now I need some expert help with the production side. As I understood, I just needed to exchange the certificate from development to production and upload this in the Parse Control Panel. Did that and still get a green mark in the test area. My Ad-Hoc signed iphones do get the push notifications, but if somebody downloads the app from the App Store, they dont get the message: "do you accept push notifications blabla.." As in Parse docs it says that in production status, both ad-hoc and app store production profiles should get the messages. So long post... Can anybody help me out?

AlanMac Aspiring developer Posts: 2612 Reg: Mar 05, 2012 Esher, UK 37,120	10/24/12 07:03 AM (13 years ago) When you created your apple certificate for adhoc distribution, it sounds like you did everything you needed to, but you need to go through all the same steps again for the production certificate. I find the parse.com end of things is a walk in the park compared to the apple process! Comments When you created your apple certificate for adhoc distribution, it sounds like you did everything you needed to, but you need to go through all the same steps again for the production certificate. I find the parse.com end of things is a walk in the park compared to the apple process!

LeonG Apple Fan Posts: 694 Reg: Nov 08, 2011 Hamburg 17,740	10/24/12 07:30 AM (13 years ago) The .p12 key for Parse is made from the App-ID and that is put to ditribution and not to development. This key should work for both distribution ways: adhoc and App Store or is that not right? And if not, what do I have to do to make it work??? Comments The .p12 key for Parse is made from the App-ID and that is put to ditribution and not to development. This key should work for both distribution ways: adhoc and App Store or is that not right? And if not, what do I have to do to make it work???

AlanMac Aspiring developer Posts: 2612 Reg: Mar 05, 2012 Esher, UK 37,120	10/24/12 10:49 AM (13 years ago) It sounds as if the parse end of things is OK, but the production cert for Apple is not registered for push notifications (and the ad-hoc cert was). Whatever you did for Apple ad-hoc does not work for production, you have to go through the process for production cert again and resubmit your app. Why do I know this? because it happened to me once as well! Comments It sounds as if the parse end of things is OK, but the production cert for Apple is not registered for push notifications (and the ad-hoc cert was). Whatever you did for Apple ad-hoc does not work for production, you have to go through the process for production cert again and resubmit your app. Why do I know this? because it happened to me once as well!

LeonG Apple Fan Posts: 694 Reg: Nov 08, 2011 Hamburg 17,740	10/24/12 10:57 AM (13 years ago) but the production part works, otherwise ad-hoc wouldnt work right?? Ad hoc is production too. Comments but the production part works, otherwise ad-hoc wouldnt work right?? Ad hoc is production too.

AlanMac Aspiring developer Posts: 2612 Reg: Mar 05, 2012 Esher, UK 37,120	10/24/12 11:18 AM (13 years ago) I think of the ad-hoc release process as adding a new development device. I think you code-sign the app with the profile which is tied to the certificate you produce for push. That worked. The production signing process uses a 'release' apple profile. It sounds to me that you did not register that to include push for this app. What I am trying to say is whatever you did for Ad-hoc was right, but you have to do it all over again for release. Comments I think of the ad-hoc release process as adding a new development device. I think you code-sign the app with the profile which is tied to the certificate you produce for push. That worked. The production signing process uses a 'release' apple profile. It sounds to me that you did not register that to include push for this app. What I am trying to say is whatever you did for Ad-hoc was right, but you have to do it all over again for release.

LeonG Apple Fan Posts: 694 Reg: Nov 08, 2011 Hamburg 17,740	10/24/12 05:01 PM (13 years ago) Well, I will do it all over again then, will let you know if that was it. Will take 2-3 weeks till the update is approved :( Comments Well, I will do it all over again then, will let you know if that was it. Will take 2-3 weeks till the update is approved :(

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.