Hi, I am migrating from react-native-push-notification as I thought this bug resided with them. Since it is happening with this library too, it must be in my code. Has anyone experienced this before?
Around 10% of the time, I am experiencing a 10s delay when opening a warm (fcm) notification. The app opens, but it takes 10s to get the "Notification opened" log. All the handlers from the docs are implemented in the index.js except for getInitialNotification and registerNotificationOpened, which are called in my 's constructor as I mentioned in one of the open issues. Cold opens are quick, just an issue with warm. I test on multiple devices simultaneously and it only happens to 1 at a time. not the same one.
Hi, I am migrating from react-native-push-notification as I thought this bug resided with them. Since it is happening with this library too, it must be in my code. Has anyone experienced this before?
Around 10% of the time, I am experiencing a 10s delay when opening a warm (fcm) notification. The app opens, but it takes 10s to get the "Notification opened" log. All the handlers from the docs are implemented in the index.js except for getInitialNotification and registerNotificationOpened, which are called in my 's constructor as I mentioned in one of the open issues. Cold opens are quick, just an issue with warm. I test on multiple devices simultaneously and it only happens to 1 at a time. not the same one.