You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a notification is send (and received) and the application is open the OneSignal.shared.setNotificationWillShowInForegroundHandler should be always executed but not alwalys is.
The notification is received with no problem.
Steps to reproduce?
In the main method before the **runApp** it is run in the folloeing order:
await OneSignal.shared.setAppId(onesignalAndroidId);
OneSignal.shared.setNotificationOpenedHandler((OSNotificationOpenedResult result) {
...
});
OneSignal.shared.setNotificationWillShowInForegroundHandler((OSNotificationReceivedEvent event) {
...
});
...
runApp(const MyApp());
What did you expect to happen?
I expected to OneSignal.shared.setNotificationWillShowInForegroundHandler always be executed since it is implemented.
OneSignal Flutter SDK version
3.5.1
Which platform(s) are affected?
iOS
Android
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hello @wbasabe0891201 apologies that this issue was missed. Are you still having this issue? If so, can you please provide the full log from the device reproducing this behavior?
I'd highly suggest upgrading to our lates major release of the Flutter SDK which includes many improvements and enhancements. Please refer to our migration guide for full details!
What happened?
When a notification is send (and received) and the application is open the OneSignal.shared.setNotificationWillShowInForegroundHandler should be always executed but not alwalys is.
The notification is received with no problem.
Steps to reproduce?
What did you expect to happen?
I expected to OneSignal.shared.setNotificationWillShowInForegroundHandler always be executed since it is implemented.
OneSignal Flutter SDK version
3.5.1
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: