[Android] getInitialNotification does not consume the notification

[ayman-kouzayha]

While using getInitialNotification on Android we noticed that the call is not consuming the notification unless the app is swiped away, if the app was started with an initial notification then sent to the background where after some time the OS could clear the UI from memory, upon relaunching the app getInitialNotification will re-provide the same notification again which does not match the description of the function in the docs.

https://notifee.app/react-native/reference/getinitialnotification

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[rodrigo-ferreira-mentorspaces]

I'm having the same problem.

[allisonadam81]

I've run into this as well.

My only solution was to check if getInitialNotification was populated. If it was, store it in async, and load the rest of the app. Then later on my app logic I have a useEffect that checks the async storage key to see if it was opened through a notification. That way I could bypass the situation by only calling getInitialNotification the one time and avoid all the false positives.

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[badhrin]

Agree...this issue is not Stale. I am facing the same issue. The same Initial Notification is populated every time the app is opened, even when opened by the user.

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[anwargul0x]

+1

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[truongnv98]

Android: For anyone using react native firebase

• background: use the messaging().onNotificationOpenedApp()
• close app: use the messaging().getInitialNotification()
• foreground app: use the notifee.onForegroundEvent()

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

@mikehardy are you able to reopen this one as I missed the stale notification before I could bump it.

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[liamjones]

Not stale

[rodperottoni]

probably related to #1043