-
Notifications
You must be signed in to change notification settings - Fork 4
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
The receiver "doctrine" does not exist. Valid receivers are: doctrine. #225
Comments
Hay @aluuraco - I'm pretty sure that your transport should be defined under |
PS, if the docs are wrong, please send a patch with a fix :) |
I found that my issue description had an error during copy and paste of the config file:
];` I'm still getting the same error message that the very same transport that I have defined, is a receiver that does not exist, even though the command would say that the transport that I parsed into the command is a valid receiver. |
🤔 As per #190, the doctrine transport factory is the only untested thing here. What version of Symfony messenger are you using? 6 or 7? In 7, (I think) the shipped doctrine factory was marked internal, so this lib might need to work out something else when it comes to using doctrine as a transport. Regardless, it's going to take me some time to figure out what the problem is and I don't have very much of that right now. Any tests that you can contribute will improve the situation 👍 |
I'm getting the strange receiver does not exist error message when trying to initiate the messenger:consume command. Does anybody know what's wrong?
For some more context, I'm using this on a stand-alone Laminas MVC project and I've created a bin/console file to initiate the Command like the following:
php bin/console messenger:consume
The bin/console is written as follows:
I've also the following config written, following the examples provided in the docs folder of this library:
The text was updated successfully, but these errors were encountered: