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

OneSignal.shared.setNotificationWillShowInForegroundHandler #690

Closed
3 tasks done
wbasabe0891201 opened this issue Jun 21, 2023 · 2 comments
Closed
3 tasks done

OneSignal.shared.setNotificationWillShowInForegroundHandler #690

wbasabe0891201 opened this issue Jun 21, 2023 · 2 comments

Comments

@wbasabe0891201
Copy link

wbasabe0891201 commented Jun 21, 2023

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?

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

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!

@jennantilla
Copy link
Contributor

Closing due to no response.

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

2 participants