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
Pinpoint notifications not opening app targeting Android 12 #2762
Comments
I was able to reproduce this issue. Looks like @sktimalsina updated the |
Any news ? I have the same problem too. |
🙋♂️ I'm having this problem too, please help 🙏 |
@tjleing I also am having this issue on 2.40.0 As far as I can tell the changes need to be made to the PinpointNotificationReceiver. This is a pretty good tutorial I found for updating this: (https://proandroiddev.com/notification-trampoline-restrictions-android12-7d2a8b15bbe2) |
This issue has been resolved and is live in v2.48.0. |
Describe the bug
When targeting Android SDK 31, notifications appear successfully, but tapping them just dismisses the notification without opening the app.
To Reproduce
Set up push notifications as described in the docs.
Set the app
targetSdk 31
.Send a push notification to the device, configured to open the app or a URL.
Tap on the push notification.
Which AWS service(s) are affected?
Pinpoint notifications for Android.
Expected behavior
Tapping the notification should open the app, deeplink, or URL set in the notification.
Environment Information (please complete the following information):
Additional context
Opening the app from a notification works fine with the targetSdk set to 30.
The relevant part of the log seems to be the following:
This seems to be related to a change in Android 12 to disallow starting activities from services or receivers that were opened by a notification.
The text was updated successfully, but these errors were encountered: