Skip to content
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

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

Closed
nmluancs opened this issue Feb 21, 2022 · 14 comments
Closed

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

nmluancs opened this issue Feb 21, 2022 · 14 comments

Comments

@nmluancs
Copy link

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
Copy link

@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
Copy link
Collaborator

answered in #828

@junebugfix
Copy link

@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
Copy link
Author

nmluancs commented Mar 7, 2022

I still got the problem with version 4.2.3 :(

@DanielEliraz
Copy link
Collaborator

please try it with 4.2.4.

@junebugfix
Copy link

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

@DanielEliraz
Copy link
Collaborator

DanielEliraz commented Mar 10, 2022

@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
Copy link

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

@nmluancs
Copy link
Author

nmluancs commented Mar 11, 2022

Still got the problem on version 4.2.4 :(

@junebugfix
Copy link

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

@junebugfix
Copy link

Just updating for the record, still experiencing this on 4.3.1

@AftabUfaq
Copy link

still have same issue on latest verions

@SchneiderOr
Copy link

Still experiencing it, any new thoughts?

@pennersr
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants