Boris Tacyniak
Boris Tacyniak
Hi @v1pu2 What do you send from the server? What's the payload ?
Hi, In the solution I suggested, you must send data-only notification. In your payload you send notification+data, which lead to not triggering `onNotification`. Use the same parameters as in `localNotification(params)`...
You must send DATA-only notification, not a notification-only or a notification with data. https://firebase.google.com/docs/cloud-messaging/android/receive#handling_messages App state | Notification | Data | Both -- | -- | -- | -- Foreground...
Hi @v1pu2! Is it ok for you ?
Hi @Yashpk789987 I'm not responsable of APNS or Firebase, please check official documentation or StackOverflow for potential delay. Regards,
Hi, Something is intercepting the notification, Check the example project and do not put `.configure()` inside a component. Regards
Hi @eddeee888, Would be better to rollback in hotfix, and set back your target change in major/feature release with migration guide. Semver is not about used or not, but public...
Hi @thisbar Did you checked existing issues ? https://github.com/zo0r/react-native-push-notification/issues?q=is%3Aissue+TypeError Regards,
Hi, You can use lazy loading of your data. Only read them once you need it. In this case, you read you data inside the App component and `onNotification`, lazy...
Just don't read the data until you need it.