Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS: Own userNotificationCenter:didRecieveNotificationResponse:withCompletionHandler is overwritten #984

Open
gotcha84 opened this issue Feb 6, 2024 · 6 comments

Comments

@gotcha84
Copy link

gotcha84 commented Feb 6, 2024

Reviving #925 as it is still an issue.

I'm facing the same issue on iOS when trying to use Notifee and Iterable. The Notifee delegate seems to be overwriting the Iterable delegate.

The culprit seems to be this block of code. It is parsing the non-Notifee notification into the notifeeNotification object which prevents the _originalDelegate from handling it in the else-if clause at the bottom of the function.

@akshay-engage
Copy link

Came across similar issue. Thanks to @gotcha84
With his PR changes issue was resolved.
Looking for you new release with this fix added

Copy link

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.

@gotcha84
Copy link
Author

Not fixed, still requires attention. @mikehardy or @helenaford - I have a PR out with a potential fix, would you be able to take a quick look and see if it's something worth pulling in?

Copy link

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.

@gezquinndesign
Copy link

Still requires attention. I'm just going to patch-package for now.

Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants