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

[question]: iOS 30 sec delay on notification receive #1533

Closed
1 task done
mstankov opened this issue Jul 18, 2023 · 3 comments
Closed
1 task done

[question]: iOS 30 sec delay on notification receive #1533

mstankov opened this issue Jul 18, 2023 · 3 comments

Comments

@mstankov
Copy link

mstankov commented Jul 18, 2023

How can we help?

Does anybody have an idea why every notification is received with a 30 second delay?

I've tested it on several different apple devices with different settings for battery, network etc and even with each setting set for best performance, the notifications from OneSignal are always received with a 30 second delay and I mean EXACTLY 30 seconds.

I can confirm that the iOS native side receives the notification after exactly 30 secs and immediately calls setNotificationWillShowInForegroundHandler on the JS side, which in turn calls complete.

react-native: 0.66.5
react-native-onesignal: latest

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jennantilla
Copy link
Contributor

Hi @mstankov thanks for reaching out! Are you sending media attachments along with your notification? Adding an image to your notification could delay it up to 30 seconds as it downloads it. Can you try omitting your image temporarily to rule this factor out? Other causes for delayed notifications are mentioned here.

If you are still having issues, would you be able to send a log from your device reproducing this issue?

Thanks!

@mstankov
Copy link
Author

@jennantilla Hi Jenna, thanks for replying. I can confirm that no image is being sent yet the delay is always exactly 30 seconds. I checked the other potential causes and that doesn't seem to be the case either. I'll check the logs and send them over.

@jennantilla
Copy link
Contributor

Hello @mstankov this issue has gone stale. I'm going to close it out but if you are still having issues please respond here and we'll be happy to investigate further!

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