iOS cannot receive first push notification when open in foreground
See original GitHub issueVersion: 3.1.2 RN version: 0.61.5
Using this version and lines from documentation
Notifications.events().registerNotificationReceivedForeground((notification: Notification, completion: (response: NotificationCompletion) => void) => {
console.log("Notification Received - Foreground", notification.payload);
// Calling completion on iOS with `alert: true` will present the native iOS inApp notification.
completion({alert: true, sound: true, badge: false});
});
I can only see the push notification alert starts from 2nd push notification, but not the first one.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:15
Top Results From Across the Web
iOS: cannot receive first push notification when app opened in ...
I'm experiencing the same issue as well. Very first notification isn't received on iOS foreground but succeeding ones are received.
Read more >Get push notification while App in foreground iOS
Apple says: If you receive local or remote notifications while your app is running in the foreground, you're responsible for passing the ...
Read more >How to Get Push Notification while iOS App is in Foreground
By default, if an iOS app gets a notification while the app is in the Foreground, the notification banner won't show up.
Read more >Push Notification Troubleshooting for iOS - Braze
Check that your app is prompting you to allow push notifications. Typically, this prompt will appear upon your first open of the app,...
Read more >Notifications Not Shown - Mobile Push
Common reasons why Mobile Push notifications are not showing on your device.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
To fix this bug in RN notifications 3.1.4, go first to
RNNotificationsStore.m
, then find the initializer and apply this changes (you can also apply this patch usingpatch-package
):I won’t put together a PR because it seems that the maintainers are not accepting/reviewing PRs, however, if @yogevbd is willing to review it, I’ll be glad to do it.
My current fix:
[RNNotifications addNativeDelegate:self];
in didFinishLaunchingWithOptions