[AC-4113] Push notifications not stable
GitHub Issue | n/a |
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2016-08-29T18:42:09.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Arrow Push |
Labels | pushnotification |
Reporter | Healthy SG |
Assignee | Shak Hossain |
Created | 2016-07-19T06:13:13.000+0000 |
Updated | 2016-08-29T18:42:10.000+0000 |
Description
The push notifications are very unstable. They stop working sometimes, then we need to clear device tokens from the appcelerator platform and re-register the devices for them to start working again.
Attachments
Hey there, Can you confirm when you have the issue? This issue is currently not valid.
Hi, On 21st July, we cleared the tokens and then subscribed 10 test devices and made sure they showed up in subscribed devices page(screenshot attached). After subscribing, we tested the push notifications using the following JSON: https://api.cloud.appcelerator.com/v1/push_notification/notify_tokens.json?key=D2xBdBZ3YqTvNVbhdL1HuzFgMhZnKPxC&pretty_json=true&channel=notification_alerts&payload={ "alert": "Test", "sound":"default", "title": "Example", "vibrate": true, "icon":"appicon" }&to_tokens=
HI, Is there any progress in resolving the issue? We are receiving alerts for our test accounts. But for TTSH(Tan Tock Seng Hospital) none of the patient accounts are receiving the alerts. We have SLAs to meet and we have to update MOHH on regular basis on the resolution. Kindly let us know the actions we need to take ASAP. Please let us know should you need any more details from our side. Thank you!
Hi Sharif, Shak, Any update on the issue? Kindly let us know. We have lot of pressure from clients. Thank you.
Hi Sharif, Shak, We have observed that the devices are being un-subscribed automatically once in few days. And the notifications are being failed with error message 1005-There is no corresponding subscriptions ... (please look at the attached screen shot) . Is it a known issue? Any work arounds ? Could you please help us on fixing this?
Hello, The issue is not reproducible in our end.