at_client_sdk
at_client_sdk copied to clipboard
Background notifications on the @platform
Lead: @cconstab
Is your feature request related to a problem? Please describe. Currently the @ application needs to be active to receive notifications. This causes problems when for example a notification for a file transfer has arrived at the secondary but there is no way to notify a device/app that is not running.
Describe the solution you'd like Notifications that can be received in a backgrounded app and or something to 'wake up' the correct app and deal with a notification
Describe alternatives you've considered None Additional context
Increasing need for this functionality in multiple apps on mobile platforms in particular
@cconstab For this https://pub.dev/packages/background_fetch was evaluated. • It works fine on Android. There might be still risk of OS killing in times of resource shortage. • On iOS, there are challenges in testing itself. A useful article enlisting the OS behaviour in this scenario (shared by Son Le): https://www.andyibanez.com/posts/common-reasons-background-tasks-fail-ios/
Next steps: We can implement it in one app and test it's behaviour in actual app usage.
@sachins-geekyants @nitesh2599 can you take a look at this issue and see if we should raise to high priority for work in PR43/44?
Yes still important and so let's bump it up to next sprint
I was thinking that the stats notification would have solved this problem. May be not.
Not on the client side.. App currently needs to be in foreground