{"action":"created","issue":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/3575","repository_url":"https://api.github.com/repos/ParsePlatform/parse-server","labels_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/3575/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/3575/comments","events_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/3575/events","html_url":"https://github.com/ParsePlatform/parse-server/issues/3575","id":210585773,"number":3575,"title":"Parse Server Crash on invalid/expired APNS cert ","user":{"login":"gateway","id":519563,"avatar_url":"https://avatars2.githubusercontent.com/u/519563?v=3","gravatar_id":"","url":"https://api.github.com/users/gateway","html_url":"https://github.com/gateway","followers_url":"https://api.github.com/users/gateway/followers","following_url":"https://api.github.com/users/gateway/following{/other_user}","gists_url":"https://api.github.com/users/gateway/gists{/gist_id}","starred_url":"https://api.github.com/users/gateway/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gateway/subscriptions","organizations_url":"https://api.github.com/users/gateway/orgs","repos_url":"https://api.github.com/users/gateway/repos","events_url":"https://api.github.com/users/gateway/events{/privacy}","received_events_url":"https://api.github.com/users/gateway/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-02-27T19:43:18Z","updated_at":"2017-03-15T15:55:48Z","closed_at":null,"body":"We use GitHub Issues for bugs.\r\n\r\nIf you have a non-bug question, ask on Stack Overflow or Server Fault: \r\n- https://stackoverflow.com/questions/tagged/parse.com \r\n- https://serverfault.com/tags/parse\r\n\r\nYou may also search through existing issues before opening a new one: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue \r\n\r\n--- Please use this template. If you don't use this template, your issue may be closed without comment. ---\r\n\r\n### Issue Description\r\n\r\nParse server 2.3.6 crashes when the push cert for apns has expired.\r\n\r\nDescribe your issue in as much detail as possible.\r\n\r\n### Steps to reproduce\r\n\r\nGet put a old apns cert in and log in as a new user.\r\n\r\n#### Actual Outcome\r\n\r\nWhat is happening instead.\r\n\r\n### Environment Setup\r\n\r\n- **Server**\r\n  - parse-server version (Be specific! Don't say 'latest'.) : 2.3.6\r\n  - Operating System:     Heroku \r\n  - Hardware:             Standard 2x\r\n  - Localhost or remote server? Heroku \r\n\r\n- **Database**\r\n  - MongoDB version: 3.2\r\n  - Storage engine:  tiger\r\n  - Hardware:        dedicated\r\n  - Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mlab.\r\n\r\n### Logs/Trace\r\n\r\nFeb 27 11:31:00 stage app/web.1:  ERR! parse-server-push-adapter APNS cannot find vaild connection for c867c8504a4657fe77070971d11644ab84f95105524a632c6b5b2738957f7e6d \r\nFeb 27 11:31:00 stage app/web.1:  /app/node_modules/parse-server/lib/ParseServer.js:460 \r\nFeb 27 11:31:00 stage app/web.1:              throw err; \r\nFeb 27 11:31:00 stage app/web.1:              ^ \r\nFeb 27 11:31:00 stage app/web.1:  Error: certificate has expired: 2017-02-10T00:33:23.000Z \r\nFeb 27 11:31:00 stage app/web.1:      at validateCredentials (/app/node_modules/apn/lib/credentials/validate.js:12:9) \r\nFeb 27 11:31:00 stage app/web.1:      at /app/node_modules/apn/lib/connection.js:163:5 \r\nFeb 27 11:31:00 stage app/web.1:      at _fulfilled (/app/node_modules/q/q.js:834:54) \r\nFeb 27 11:31:00 stage app/web.1:      at self.promiseDispatch.done (/app/node_modules/q/q.js:863:30) \r\nFeb 27 11:31:00 stage app/web.1:      at Promise.promise.promiseDispatch (/app/node_modules/q/q.js:796:13) \r\nFeb 27 11:31:00 stage app/web.1:      at /app/node_modules/q/q.js:604:44 \r\nFeb 27 11:31:00 stage app/web.1:      at runSingle (/app/node_modules/q/q.js:137:13) \r\nFeb 27 11:31:00 stage app/web.1:      at flush (/app/node_modules/q/q.js:125:13) \r\nFeb 27 11:31:00 stage app/web.1:      at _combinedTickCallback (internal/process/next_tick.js:67:7) \r\nFeb 27 11:31:00 stage app/web.1:      at process._tickDomainCallback (internal/process/next_tick.js:122:9) \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Linux 3.13.0-105-generic \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! argv \"/app/.heroku/node/bin/node\" \"/app/.heroku/node/bin/npm\" \"start\" \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! node v7.6.0 \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! npm  v4.1.2 \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! code ELIFECYCLE \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! parse-server-example@1.4.0 start: `node index.js` \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Exit status 7 \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR!  \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Failed at the parse-server-example@1.4.0 start script 'node index.js'. \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Make sure you have the latest version of node.js and npm installed. \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! If you do, this is most likely a problem with the parse-server-example package, \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! not with npm itself. \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Tell the author that this fails on your system: \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR!     node index.js \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! You can get information on how to open an issue for this project with: \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR!     npm bugs parse-server-example \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Or if that isn't available, you can get their info via: \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR!     npm owner ls parse-server-example \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! There is likely additional logging output above. \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR! Please include the following file with any support request: \r\nFeb 27 11:31:00 stage app/web.1:  npm ERR!     /app/npm-debug.log "},"comment":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/comments/286787545","html_url":"https://github.com/ParsePlatform/parse-server/issues/3575#issuecomment-286787545","issue_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/3575","id":286787545,"user":{"login":"flovilmart","id":364568,"avatar_url":"https://avatars0.githubusercontent.com/u/364568?v=3","gravatar_id":"","url":"https://api.github.com/users/flovilmart","html_url":"https://github.com/flovilmart","followers_url":"https://api.github.com/users/flovilmart/followers","following_url":"https://api.github.com/users/flovilmart/following{/other_user}","gists_url":"https://api.github.com/users/flovilmart/gists{/gist_id}","starred_url":"https://api.github.com/users/flovilmart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flovilmart/subscriptions","organizations_url":"https://api.github.com/users/flovilmart/orgs","repos_url":"https://api.github.com/users/flovilmart/repos","events_url":"https://api.github.com/users/flovilmart/events{/privacy}","received_events_url":"https://api.github.com/users/flovilmart/received_events","type":"User","site_admin":false},"created_at":"2017-03-15T15:55:48Z","updated_at":"2017-03-15T15:55:48Z","body":"Not sure that's our responsibility in this module, probably in APNs https://github.com/node-apn/node-apn/issues/541 \r\n\r\nFollow the discussion here and open a PR if you need too.\r\n"}}
{"actor":{"display_login":"flovilmart"}}