Cloud messaging report say successful send 1 but no notification send or visible in firebase console about laravel-firebase HOT 6 CLOSED

Unfortunately, there is no way of telling from our side whether there is a problem with message delivery. The Firebase console doesn't display messages sent over the Firebase APIs, and we can only say:

If the Firebase API doesn't return an error, we can assume:

• the message was syntactically correct
• the target of the message exists (in case of an invalid, expired or non-existing registration token for the current project, topics and conditions always work)
• The Firebase API has accepted the message (that's represented by the "success")

From there on it's out of our vision - we can't tell when the message will be actually delivered or if it will be delivered at all. In the past years it was sometimes the case that https://status.firebase.google.com/ et.al. was green, but the APIs returned errors, or that messages took hours to arrive at their target.

Sometimes the notification was received at the target, but the app didn't recognize it or crashed, or the message was a data only message and didn't trigger a notification on the target device(s) (your message contains a notification, so that wouldn't apply).

Long story short: Sadly I'm unable to give you more information from the SDK perspective, but perhaps https://firebase.google.com/support/troubleshooter/fcm/delivery/diagnose can provide some further help 🤞

from laravel-firebase.

Am I the only one to face problems to send notifications with your library ? My code seems correct, otherwise I would get an error ?
Is there an update on fcm that your library don't support ?
Thank you for your answer.

from laravel-firebase.

No, you're not the only one, but it's rather rare that I hear of issues like this (or, if there are more, they don't get reported). But again: your code is correct, and the library works (otherwise you would get an error because Firebase rejects the requests).

Of course, the SDK will always be "late": if a new feature or change is implemented by Firebase, this SDK will only implement it later - but if you don't get an error, it should be fine on the SDK level.

from laravel-firebase.

Ok, thanks for your reply, I will investigate on my side because I can't give up this feature for my backoffice application. All advices are welcomed.

from laravel-firebase.

I'm closing this now, but feel free to add further comments or create a new issue.

FYI: If the issue is with the Laravel Package, create a new issue, here. If it's an issue with the functionality, open an issue at https://github.com/kreait/firebase-php

from laravel-firebase.

from laravel-firebase.