-
Notifications
You must be signed in to change notification settings - Fork 1k
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
bug: Onesignal notification not shown on iOS with the app in foreground #5542
Comments
This comment was marked as abuse.
This comment was marked as abuse.
it seems that my ugly workaround doesn't reset the unread notification badge |
@fabioz23 It looks like there is a setting named capacitor/ios/Capacitor/Capacitor/CAPInstanceDescriptor.h Lines 86 to 90 in 2b7016f
However not sure where you would set this to |
Same problem here, any update? |
next release of Capacitor (probably 4.4.1) will allow to set handleApplicationNotifications to false so OneSignal and other plugins can have the notification center for themselves. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out. |
Bug Report
Capacitor Version
Platform(s)
iOS
Current Behavior
After project upgrade (from [email protected], [email protected] to [email protected], [email protected]) Onesignal push notification not shown when the app is in foreground.
This happens despite having configured the proper handler for foreground notifications like Onesignal wiki suggest.
Expected Behavior
Inbound Push Notification shown by OS
Code Reproduction
Other Technical Details
npm --version
output: 8.5.5node --version
output: v14.17.0pod --version
output (iOS issues only): 1.11.3Additional Context
My workaround is to forcibly disable handleApplicationNotifications member of NotificationRouter class:
After doing this i was capable to receive push notification on iOS and the app in foreground.
The text was updated successfully, but these errors were encountered: