搞砸Apple Push Notification Service

Question

I have been developing an app that uses push notifications. I have been messing around ALOT trying to fix the stupid provisioning stuff, and I really don't know what's what anymore.

I managed to fix the whole development push notifications. And now, we are close to release. However, the switch to Production notification didn't go as smooth as expected. And I still don't really understand the whole provisioning-thing.

I thought I just had to switch out the .pem file with a new one, generated from a new .cer and .p12 file, aswell as remove the "sandbox" from the url it's trying to connect to. This just resulted in "Failed to connect: 0" in my .php sending the push.

.php

$ctx = stream_context_create();
stream_context_set_option($ctx, 'ssl', 'local_cert', 'dp.pem')
stream_context_set_option($ctx, 'ssl', 'passphrase', $passphrase);

$fp = stream_socket_client(
    'ssl://gateway.push.apple.com:2195', $err,
    $errstr, 60, STREAM_CLIENT_CONNECT|STREAM_CLIENT_PERSISTENT, $ctx);

if(!$fp)
    exit("Failed to connect: $err $errstr" . PHP_EOL);

After messing around with the .p12 and .cer and .cert and .pem and .mobileprovision .ipa, I really don't know what to do anymore.. Why do we have to convert to .pem and merge them? Is this REALLY the way Apple intended for us to do this? Or have I been following a pretty redicolus tutorial?

What .cer file do I need? Which profile should the app use? AppID vs provision vs device vs Certificate. What the hell.. Should I have to do anything other than switching to a new .pem file and remove the "sandbox". I have activated and downloaded the "Production Push SSL Certificate" from the portal, and generated my .pem file from that. I have tried reading up on this, but it is reeeally hard and a stupid setup! I'm sure I have done something wrong. But can't figure out what, where and why!

Answer 1

推送通知服务 -很棒的教程，您将找到php脚本+回答所有问题。