Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
The full error:
Whoops\Exception\ErrorException : Trait method credentials has not been applied, because there are collisions with other trait methods on Laravel\Spark\Http\Controllers\Auth\PasswordController
at /home/vagrant/code/vendor/laravel/spark-aurelius/src/Http/Controllers/Auth/PasswordController.php:11
7| use Laravel\Spark\Http\Controllers\Controller;
8| use Illuminate\Foundation\Auth\ResetsPasswords;
9| use Illuminate\Foundation\Auth\SendsPasswordResetEmails;
10|
> 11| class PasswordController extends Controller
12| {
13| use SendsPasswordResetEmails, ResetsPasswords {
14| SendsPasswordResetEmails::broker insteadof ResetsPasswords;
15| }
This is weird because I haven't changed the spark package in a while. This error happens when I run
php artisan route:list
This was not happening yesterday. Rolled back to yesterday's commit to see what happened. This issue remains...
When I comment out the crendentials function on either of the traits listed in the error, route:list works just fine. But I obviously don't want to modify vendor packages, so what else might be causing this?
I did a full project search, and the function credentials only appears in these two traits and AuthenticatesUsers.
Only the ResetPasswords trait has that method as far as I can see.
https://github.com/laravel/framework/blob/master/src/Illuminate/Foundation/Auth/ResetsPasswords.php#L83 https://github.com/laravel/framework/blob/master/src/Illuminate/Foundation/Auth/SendsPasswordResetEmails.php
What Laravel version are you using? It could be an old bug
@BOBBYBOUWMANN - @bobbybouwmann
That is really weird. in my composer.json, I have this: "laravel/framework": "5.8.*",
I also deleted the entire vendor folder just now and reinstalled it. Sure enough, SendsPasswordResetEmails came back with a credentials method again...
Aah you're right! I see that there is a credentials method in 5.8, I send you the link of the master branch!
@number6 I think we should create a new issue on the framework, but i've given them some context already ;)
@BOBBYBOUWMANN - Thanks for pointing that out.
I suppose the quickest short term solution is to override the spark controller to fix that issue until the two packages resolve this conflict?
just saw your comment. Thanks for reporting it!
@number6 Yeah, just override one of the trait methods or the controller and you should be good to go! It's a nasty work around though. If you want you can create a new issue on the repo, not sure if this will be reverted without an issue.
@BOBBYBOUWMANN - I imagine this is a spark bug, not framework? Can I even report issues or do I just email them?
You can create issues here: https://github.com/laravel/framework/issues
It's both a Spark and Laravel bug in this case. Because I can also include both traits in a Laravel application and would have the same problems.
@number6 I went ahead and created an issue for you: https://github.com/laravel/framework/issues/28377
@number6 It's fixed :D https://github.com/laravel/framework/issues/28377
Please or to participate in this conversation.