This question is locked. New answers and comments are not allowed.
I have noticed a long lapse between the time I "create" a notification, and the time that it gets "sent". I always set the time of delivery to "now", but there is usually a delay between two and a half hours and all the way up to four days. What accounts for this discrepancy?
Also, if a device has been activated to receive push notifications, does it need to be actively running in order for the notifications to be received by the device? It appears that in most cases (at least on the phones that I test with), that the app must actually be open in order for the notification to come through.
Also, if a device has been activated to receive push notifications, does it need to be actively running in order for the notifications to be received by the device? It appears that in most cases (at least on the phones that I test with), that the app must actually be open in order for the notification to come through.
1 Answer, 1 is accepted
0
Hello Michael,
In regard to your first question, I guess you refer to push notifications sent from the portal.
A push notification is sent with little to no delay after it is successfully created to the corresponding push notification server (Apple Push Notification Server, Google Cloud Messaging, Windows Push Notification Service) along with its payload, expire date, etc. It takes a while to update the status for the message in the portal to 'Sent' and several hours (at average) to aggregate the 'Devices' count.
In regard to delivery, the app could be in the background and a badge, banner or sound (or combination of them) for iOS, and an icon in the notification bar in Android, will prompt the user that something interesting is happening. Then the user must tap the icon of the app, the banner, or the message in the notification bar in order to open the app.
Push notifications can also be received when the app is closed unless they are explicitly stopped by the user (in which case notifications will not reach the app until it is restarted by the user).
Could you please explain in more details your use case and the behavior of the app when in foreground/background and the platform of the device(s)?
Regards,
Anton Dobrev
Telerik
In regard to your first question, I guess you refer to push notifications sent from the portal.
A push notification is sent with little to no delay after it is successfully created to the corresponding push notification server (Apple Push Notification Server, Google Cloud Messaging, Windows Push Notification Service) along with its payload, expire date, etc. It takes a while to update the status for the message in the portal to 'Sent' and several hours (at average) to aggregate the 'Devices' count.
In regard to delivery, the app could be in the background and a badge, banner or sound (or combination of them) for iOS, and an icon in the notification bar in Android, will prompt the user that something interesting is happening. Then the user must tap the icon of the app, the banner, or the message in the notification bar in order to open the app.
Push notifications can also be received when the app is closed unless they are explicitly stopped by the user (in which case notifications will not reach the app until it is restarted by the user).
Could you please explain in more details your use case and the behavior of the app when in foreground/background and the platform of the device(s)?
Regards,
Anton Dobrev
Telerik
Everlive is now Telerik Backend Services, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)