-
Notifications
You must be signed in to change notification settings - Fork 766
NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked #884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Downgrading targetSdkVersion to 30, solves the issue, the notification is still flagged as indirect but is not blocked. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I'm seeing this issue with v4.3.1. |
The issue has been closed for inactivity. |
I am also seeing this issue with 4.3.1 |
Solved by downgrading targetSdkVersion = 31 to targetSdkVersion = 30 in build.gradle Edit : Unfortunatly with this change in targetSdkVersion, you cannot deploy on google play store your app because it now requires at least version 31 for security reasons. |
Still seeing the issue even with |
Same here. Can this be reopened?? |
When app is killed notification is created by firebase so we need to update firebase core library for targetSdkVersion>30.
|
Thank you @asdemura, I was facing the same issue and your fix did the trick 👍 |
This seems to still be an issue with version @asdemura 's workaround fixes the issue for us. |
Thank you @asdemura, I fixed my issue and the app works well |
On Android 12, when app is killed or in background, tapping the notification does not open the app.
Adb logcat shows : NotificationService: Indirect notification activity start (trampoline) from com.xxx.xxx blocked
Turning off NOTIFICATION_TRAMPOLINE_BLOCK in App Compatibility Changes makes the app open after tapping the notification.
"react-native-notifications": "^4.3.1"
"react-native": "0.68.2"
build.gradle
manifest
`
The text was updated successfully, but these errors were encountered: