-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Laravel 10.41.0 notifications fail to send #49790
Comments
Hit @SimondeJong-VinvuSoftware. Could you maybe pinpoint the exact version which causes this for you to fail? |
Hi @driesvints , Thanks for your help. It seems the issue arrises from v10.33.0 and higher |
I found the specific commit which seems to be breaking; 4bc11bb. The function
This means when the
|
… not counted as sent Resolve bug found in issue laravel#49790
So I suspected that PR was the culprit as I faced a similar issue while working on laravelio/laravel.io#979 @SimondeJong-VinvuSoftware but it turns out in the end the PR was correct. If there's no channels returned from the notification then there's no notifications to be sent. In fact, the previous behaviour was a faulty one and perhaps something people like you and me relied on on a false note. I don't know how your notifications look like but you should make sure they send back the correct channels through the |
@driesvints , Thanks for your help. You are indeed correct that I relied on the incorrect behaviour. I will update my notifications to fix the issue. |
Laravel Version
10.41.0
PHP Version
8.2.2
Database Driver & Version
SQLite 3.43.2
Description
After updating Laravel from v10.32.1 to v10.42.0, my unit tests focussing on the sending of a notification fail. It seems the notifications are not sent. The unit test passes without issues on v10.32.1. Thanks in advance for any help!
Steps To Reproduce
An example of a failing unit test is:
And example of the controller method is as follows:
All unit tests which test the sending of notifications seem to fail.
The text was updated successfully, but these errors were encountered: