You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just finished updating my server and didn't have the push notification .p12 files on the new instance. When I tried to send a push notification using the server, not only did it not go through, but the server instance crashed.
Steps to reproduce
Add the certificate properties in your index.js file
Do not have your .p12 files in the location specified
Send a push
Expected Results
Verbose about missing .p12 files and no pushes actually sent out ONLY
Actual Outcome
Verbose and server crash
Environment Setup
Server
parse-server version: 2.2.13
Operating System: Ubuntu 15.10
Hardware: 4 GB Memory / 60 GB Disk / NYC3
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Digital Ocean
Database
MongoDB version: 3.2.7
Storage engine: N/A
Hardware: 4 GB Memory / 60 GB Disk / NYC3
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): Digital Ocean
Was there no output when the server crashed? Wondering how obscure the issue would be when someone runs into this, and if its worth handling as a special case.
There was but I was in a rush to fix it because my production app relies on the server. I think this is not obscure at all, just remove the .p12 files from the location specified in your index.js and send a push.
Activity
hramos commentedon Jun 22, 2016
Was there no output when the server crashed? Wondering how obscure the issue would be when someone runs into this, and if its worth handling as a special case.
acegreen commentedon Jun 23, 2016
There was but I was in a rush to fix it because my production app relies on the server. I think this is not obscure at all, just remove the .p12 files from the location specified in your index.js and send a push.
jeffreyjackson commentedon Jul 6, 2018
I ran into an issue today where the push certificate had expired and as a result parse server was unresponsive and continued to crash.
flovilmart commentedon Jul 6, 2018
Closing as it’s an issue in the node-APN module. If you want it fixed, open the issue there
jeffreyjackson commentedon Jul 6, 2018
I found the issue on the parse server push adapter module. Thanks!