[Android] onForegroundEvent or onBackgroundEvent not triggering when clicking push notifications

[LuckyMadu]

I must navigate to a specific screen based on the data object information. iOS is working fine for this issue.

 "react-native": "0.72.0"
 "@notifee/react-native": "^7.8.0"

notifee.onForegroundEvent(({ type, detail }) => {
    if (type === EventType.PRESS) {
        // access data
    }
  });

Below is the Postman payload to send the push notification.

{
    "message": {
        "token": "xxx",
        "notification": {
            "body": "Welcome to management",
            "title": "Welcome"
        },
        "data": {
            "id": "12345",
            "type": "Document"
        }
    }
}

[github-actions[bot]]

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.

[Gautham495]

Having the same issue suddenly. It worked before for me. Please fix this.

[github-actions[bot]]

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.

[Eclipses-Saros]

not stale

check https://github.com/invertase/notifee/issues/621#issuecomment-2342711032

[github-actions[bot]]

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.

[mikehardy]

This may be fixed in v9.1.2 here - there was definitely a problem with new architecture if it was in use, and it would not work until v9.1.2 just now

[github-actions[bot]]

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.