{ "id": "134275", "key": "AC-1041", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12217", "key": "AC", "name": "Appcelerator - INBOX", "projectCategory": { "id": "10000", "description": "", "name": "Customer Service" } }, "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2014-10-15T02:15:26.000+0000", "created": "2014-08-07T00:31:34.000+0000", "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "sliang", "key": "sliang", "displayName": "Shuo Liang", "active": true, "timeZone": "Asia/Harbin" }, "updated": "2016-03-08T07:37:23.000+0000", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "14548", "name": "Titanium SDK & CLI", "description": "Please enter tickets related to the MobileSDK here." } ], "description": "So I received the below email from appcelerator. \r\nWe have a live app with no config changes on ACS, or within the apple developer portal for a few weeks. I called Apple to see if they are having any certificate or push notification issues on their side, but they weren't. We also checked our Apple portal and the cert was definitely active and unexpired.\r\nIn this case, after my call with Apple, we immediately went back just tried clicking \"Enabled\" and it re-accepted our certificate without any changes.\r\n\r\nSo I'm thinking ACS on first sign of a glitch in the response or network connectivity, deactivated my .p12 certificate immediately on ACS. \r\n\r\nMy app has messaging features, so this is highly critical as if ACS auto-deactivated my notification in the middle of the night while my team is asleep, my international clients would be without crucial push notification for messages, leading to business loss!\r\n\r\nI think there should be a longer time-out window or other redundancies where failures are accepted. Can you guys look into this?\r\n\r\n----------------------------------------------------------------------------------------------\r\n\r\nPush notification services to iOS devices from your Appcelerator Cloud Services (ACS) app have been disabled due to invalid iOS push certificate:\r\n\r\nName: [company name]\r\nKey: ----------------------------------------\r\n\r\nRe-enable push notifications to your app by going to Application Settings under the ACS web management console and updating your iOS push certificate.\r\n\r\nThanks,\r\nThe Appcelerator Cloud Services Team", "attachment": [], "flagged": false, "summary": "Push Notification certificate revoke", "creator": { "name": "trevor_chong", "key": "trevor_chong", "displayName": "Trevor Chong", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "trevor_chong", "key": "trevor_chong", "displayName": "Trevor Chong", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "iOS", "comment": { "comments": [ { "id": "317477", "author": { "name": "sliang", "key": "sliang", "displayName": "Shuo Liang", "active": true, "timeZone": "Asia/Harbin" }, "body": "Hi,\r\n\r\nOur design is creating multiple connections to APNS with in one instance, so once there is a glitch in the response from APNS, we will deactivated the certificate in 15 mins. That is aim to protect other connections' usage. \r\n\r\nAs long as your certificate is fine, you can simply enable your certificate. This is a kind of alert to tell you checking the certificate.\r\n\r\nBased on your case, there may be a handshake_failure return from APNS, and the possibility of this happening is very low. Most of customers who received this email will have actual certificate problem. So there is no need to worry about this happens a lot. However, if this problem occurs recurrently, please feel free to contact us.\r\n\r\nRegards,\r\nShuo", "updateAuthor": { "name": "sliang", "key": "sliang", "displayName": "Shuo Liang", "active": true, "timeZone": "Asia/Harbin" }, "created": "2014-08-07T09:57:56.000+0000", "updated": "2014-08-07T09:57:56.000+0000" }, { "id": "318032", "author": { "name": "dmitri_a", "key": "dmitri_a", "displayName": "Dmitri", "active": true, "timeZone": "America/New_York" }, "body": "I had this issue happen twice, both times I just clicked \"Enabled\" again and it started working again.\r\nPlease fix this issue.\r\n", "updateAuthor": { "name": "dmitri_a", "key": "dmitri_a", "displayName": "Dmitri", "active": true, "timeZone": "America/New_York" }, "created": "2014-08-11T18:26:55.000+0000", "updated": "2014-08-11T18:26:55.000+0000" }, { "id": "318109", "author": { "name": "sliang", "key": "sliang", "displayName": "Shuo Liang", "active": true, "timeZone": "Asia/Harbin" }, "body": "Hi,\r\n\r\nSorry about the inconvenient. For now, we temporary close this feature about handshake_failure from APNS as a workaround. Then we will address the problem as soon as we can.\r\n\r\nRegards,\r\nShuo", "updateAuthor": { "name": "sliang", "key": "sliang", "displayName": "Shuo Liang", "active": true, "timeZone": "Asia/Harbin" }, "created": "2014-08-12T00:32:16.000+0000", "updated": "2014-08-12T00:32:16.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }