4 ms·
It solved "delayed notifications" for me, for certain: I still have original Samsung next to iPhone and it's clear as day: - iPhone rings, Samsung nothing - I
by eurekin 3y ago
It solved "delayed notifications" for me, for certain: I still have original Samsung next to iPhone and it's clear as day:
- iPhone rings, Samsung nothing
- I wait few minutes just to be sure and pick up Samsung - immediately after picking it up the notification shows up, with the exact timestamp of the moment I picked it up
That's why I called it a tangent to XMPP
- londons_explore 3y agoI think this is because iphone has never allowed background apps to hold open persistent connections, yet android does but with device and power-state specific limitations. So the iphone version of any xmpp app has to use apples notification service, but the android version of the same app might try to use a direct connection (saving the app developer a lot of server costs), even though on many models of phone it only works when the device is charging for example.
- lightedman 3y agoMost android devices do that - sleep-state an application and it won't tell you anything until you actively pick up the device and use it. Been like that since I had my Kyocera DuraForce Pro on Android 6 or 7.
- eurekin 3y agoYes, and there is an option to opt-out of that list. I did enable that. I'll phrase my issue differently: Is there any way to have reliable notification delivery that are time critical? Is actually calling the only 100% reliable option, as the PagerDuty does?
- londons_explore 3y agoPush notifications via play services are the only reliable way. They work even with battery saver on (but not extreme battery saver, unless the app is excluded). Note that you can only have one push notification reliably per user interaction. So once you have sent a notification, further ones won't be reliably delivered until the user interacts with your app in some way.
- eurekin 3y agoThat's perfect, thank you!