-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Android action handlers in JS not triggered #590
Comments
For what use cases do the foreground of false work? I tested it when the app is suspended and still don't see the callbacks getting invoked. Any idea when the issue maybe resolved (for firing callbacks when the app is in a terminated state or the background state) |
@sanmed when the app is in the background and you set foreground to false on your action button the callback does get called. At least I see my callback get invoked when I attach a debugger to the app. As for how to fire a callback when the app is terminated, no set timetable. Ideally you should not terminate the app but I understand that users do kill apps. So pull requests are welcome 😄 |
Thanks Simon. Do you have any updates on this? We'd really like the interactive push notifications to work when the app is in the terminated state :) Any help on this is appreciated. Also, can you provide your contact info as I'd like to run by you a few questions I have? Thanks |
passing data with action button, because when app is closed and notification is going to come and when we click on action button the callback is call but how to catch data with this click |
I am using 1.6 and have set the foreground to false in the payload. When the app is terminated and a push notification comes through, clicking on the buttons doesn't trigger the JS handlers. Here's what I see in the logcat log
I do log the entry point for the triggers in JS and don't see them in the logcat logs.
Is foreground set to false expected to work in the coldstart/in memory scenarios?
The text was updated successfully, but these errors were encountered: