-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Queueing support #6
Comments
Hi @zepfietje! It should support queueing. Does your notification implement Laravel's |
Yes, and it works fine locally. However, running in production it fails with the following exception: |
Strange. That often means that namespaces are not correctly configured as Laravel cannot find them. Can you optimize your local environment and try again locally or clear the application cache in production? Maybe it's a caching issue. |
What do you mean by "optimize your local environment"? |
The |
After running |
I verified it working locally both queued, unqueued, optimized and non-optimized. In all cases the notification was sent. Can you check if you;
If none of it works, I would try to dump the composer autoload files again to ensure the class is autoloaded. Also, some (example) code would help ;) |
It's working locally now (not sure what fixed it). I'm not doing anything special with the notification, so probably it's not related to this package (but rather a caching issue indeed). |
When running |
The package should be autodiscovered. It was in my test setup. Are you using Laravel 5.5 or higher? |
Yep, latest Laravel version. |
@MSnoeren I'm still running into this issue. |
Okay, finally solved it by running |
It seems like this package currently doesn't support queued notifications?
The text was updated successfully, but these errors were encountered: