Cordova platform version (cordova platform ls): android 10.1.1
Expected Behavior
On Android 12, after an app is killed or in the background, tapping on a notification does not open the app. Adb logcat shows the following:
NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked
The same happens when 2 and 3 notifications from the same app have been queued up.
However, when more than 3 notifications are queued and these notifications are grouped together, tapping on any of these notifications opens up the app.
Happy to do any testing to further debug.
Actual Behavior
App should open with tapping a single notification
Steps to Reproduce
When a single notification is triggered, tap on it. App is not opened.
When 2 or 3 notifications are triggered, tapping on any of them doesn't open the app.
When notifications are grouped, tapping on any of them opens up the app.
Context
Open app when tapping notification
Debug logs
NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked
WARNING: IF YOU IGNORE THIS TEMPLATE, WE'LL IGNORE YOUR ISSUE. YOU MUST FILL THIS IN!
Provide a general summary of the issue.
Your Environment
cordova -v): 11.0.0cordova platform ls): android 10.1.1Expected Behavior
On Android 12, after an app is killed or in the background, tapping on a notification does not open the app. Adb logcat shows the following:
NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked
The same happens when 2 and 3 notifications from the same app have been queued up.
However, when more than 3 notifications are queued and these notifications are grouped together, tapping on any of these notifications opens up the app.
Happy to do any testing to further debug.
Actual Behavior
App should open with tapping a single notification
Steps to Reproduce
Context
Open app when tapping notification
Debug logs
NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked