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

Cannot Capture FCM Response #211

Closed
artem-dev2 opened this issue Nov 11, 2024 · 4 comments
Closed

Cannot Capture FCM Response #211

artem-dev2 opened this issue Nov 11, 2024 · 4 comments

Comments

@artem-dev2
Copy link

I need to capture and log the response from FCM (e.g., to verify successful delivery or log errors), but it seems there’s no direct way to access the response after sending a notification.

Could you please tell me if there is a way or a woraround on this to capture thr response, Thx.

@dwightwatson
Copy link
Collaborator

So looks like right now I only fire the NotificationFailed event which means you don't have an opportunity to inspect successful responses.

Do you want to test out this PR #212 in your app and see if dispatching NotificationSent solves your issue?

@artem-dev2
Copy link
Author

I'm testing your PR the last two days and it works fine for me.
Looking forward to have this marged to main branch.

@dwightwatson
Copy link
Collaborator

Thanks for that - tagged 4.4.0.

@dwightwatson
Copy link
Collaborator

Looks like this release broke some backwards compatibility, and these events were previously fired by Laravel. You should be able to continue listening to the NotificationSent event to handle the response as you need. I apologise for the mistake.

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

No branches or pull requests

2 participants