wix / react-native-notifications

React Native Notifications
MIT License
3.25k stars 764 forks source link

When open local notification, app will open again (Version 4.2.1) #825

Closed nmluancs closed 2 years ago

nmluancs commented 2 years ago

After you fixed Android API 31 issues (Notification trampoline), now when i open a local notification, app will be cloded and open again. It happens not only on android 12 but android 11.

I think the problem comes from line 17 - 22 https://github.com/wix/react-native-notifications/blob/master/lib/android/app/src/main/java/com/wix/reactnativenotifications/core/NotificationIntentAdapter.java

Please have a look. Thank you

claudiozam commented 2 years ago

@nmluancs i have the same problem on android 12 and 11. Tested on emulator and real devices (Samsung S10, S20).

"react-native": "0.67.2" "react-native-notifications": "^4.2.0"

DanielEliraz commented 2 years ago

answered in #828

junebugfix commented 2 years ago

@DanielEliraz I'm still experiencing this with version 4.2.3, also I don't see local/foreground notifications mentioned anywhere in #828, is this a different issue?

nmluancs commented 2 years ago

I still got the problem with version 4.2.3 :(

DanielEliraz commented 2 years ago

please try it with 4.2.4.

junebugfix commented 2 years ago

@DanielEliraz Hmm, I'm still seeing the same behavior on 4.2.4

DanielEliraz commented 2 years ago

@hankhester, the trampoline error is only when targetSkdVersion > 30. current React Native targetSkdVersion is 30 so we're good in that. which targetSkdVersion do you use?

junebugfix commented 2 years ago

@DanielEliraz my targetSdkVersion is 31 - behavior is reproduced on emulators running both api 30 and 32

nmluancs commented 2 years ago

Still got the problem on version 4.2.4 :(

junebugfix commented 2 years ago

@DanielEliraz any update on this? Looks like react-native recently bumped the targetSdkVersion to 31

junebugfix commented 2 years ago

Just updating for the record, still experiencing this on 4.3.1

AftabUfaq commented 2 years ago

still have same issue on latest verions

SchneiderOr commented 2 years ago

Still experiencing it, any new thoughts?

pennersr commented 1 year ago

Can we reopen this? The issue persists in 4.3.3 with targetSdkVersion = 31.