Why am I getting Target class [Controller Name] does not exist

Question

I always have this message:

Illuminate\Contracts\Container\BindingResolutionException Target class [MessagesController] does not exist.

On some route and URL requests,

MessagesController however is not contained on my route web files, and in any of my controllers.

Can someone explain to me why the Controller class gives a warning?

Target class [MessagesController] does not exist.

Follow-up question, is there a way I can remove an unused controller by an artisan command?

Does this answer your question? Target class does not exist. problem in laravel 8 — Kamlesh Paul
– Kamlesh Paul, Commented Feb 15, 2021 at 6:23
Does this answer your question? Target class controller does not exist - Laravel 8 — I. Antonov
– I. Antonov, Commented Jun 7, 2021 at 5:28
Yes, sorry Kamlesh and Paul, this is already been solved. My bad I didn't use the class MessageController inside routes on web.php. — Philanthropist
– Philanthropist, Commented May 30, 2022 at 11:24
Yes I think, but I can't barely recall, but in this page I believe it's been resolved by importing the MessageController when accessing the controller. — Philanthropist
– Philanthropist, Commented Feb 18, 2023 at 12:13

Philanthropist · Accepted Answer · 2022-08-07 12:53:00Z

The solution I made for this is to import MessagesController class, I'm so dumb I didn't figured it out.

On route:

use App\Https\Controller\MessagesController;

1 Answer 1