Push notifications no longer working in new project with the same PEM certificates.

I use to see something like the following in my terminal when my push notifications worked:

'Push.Configure { apn:
I20161217-12:49:29.161(-5)? { keyData: 'Bag Attributes\n friendlyName: Squirrel\n localKeyID: 96 C6 23 76 AF 14 42 A8 5D 5B 59 75 89 C2 CD 9E 60 E6 7C E9 \nKey Attributes: \n-----BEGIN RSA PRIVATE KEY-----\nProc-Type: 4,ENCRYPTED\nDEK-Info: DES-EDE3-CBC,02DBA74C0930D144\n\nTGWdbyQtfWMV/0vLeg82b8OAcSE2PKoPwNRG5I5wGGnTAYcyy6xHNX2TWBBTC5uC\n1QLsGhcan93n1OeLiIlnrKMmPD9kIn4IPqciNRvyWDQImVoGgjVh3hFnQytMfYop\nSvxMR74rA4d3xDIYt8ez3fckIEavCUcfwG1Lm55gFeWmQyP3MJFxIgwvTdaSTc4M\nXmlx14ACB7AheY2ruhVzpDGfTxR88Q3feMrerh63PeVc/8eVNJwhpm2gbF+vf8V7\nGptzc7sEzErVn1u0YjT1GoP...'

But in a new project I do not see this and I think that is why my push notifications are no longer sending. I copied over the same private folder with the same Pem certificates. What am I missing?

The app still asks to allow push notifications but does not send any. My config.push.json files looks like this:

'{
"apn": {
"passphrase": "*******",
"key": "MemryKey.pem",
"cert": "MemryCert.pem"
},
"apn-dev": {
"passphrase": "********",
"key": "MemryKey.pem",
"cert": "MemryCert.pem"
},
"production": false,
"badge": true,
"sound": true,
"alert": true,
"vibrate": true
}'

Start by reviewing config.push.json and the copied private folder containing MemryKey.pem and MemryCert.pem, then compare the new project’s push setup with the reported Push.Configure output. Done means identifying why the new project does not initialize push notifications despite the same certificates and documenting the required configuration.

Written by the indexing model from the issue text.