Thanks for your input @crynobone, but this doesn't solve the full problem. The problem still exists if you use just console.php route file.

This change introduces a new issue where you cannot use both ->withSchedule() on app bootstrap AND console.php route file. You can observe this by having a task scheduled in both places and running php artisan schedule:list.

Note: inspire is scheduled inside console.php (comes by default in new install) and test is scheduled inside bootstrap.

Before this change:

After this change:

You should defer resolving code dedicated for Schedule if console.php. The file itself needs to be loaded for all artisam requests.

You are correct, I forgot the fact that console.php is used for more than just schedule.

So the only issue I see now is that both methods cannot be used simultaneously while it could have been before.

So the only issue I see now is that both methods cannot be used simultaneously while it could have been before.

As in Laravel 10? It should only be possible to register Schedule within App\Console\Kernel::schedule(). So this should make withScheduling() behave similar to the old method.

As in Laravel 11 before this change. I'll re-itterate my previous message.

This change introduces a new issue where you cannot schedule commands in both ->withSchedule() on app bootstrap AND console.php route file. You can observe this by having a task scheduled in both places and running php artisan schedule:list.

Note: inspire is scheduled inside console.php (comes by default in new install) and test is scheduled inside bootstrap.

Before this change:

After this change:

With this change ->withSchedule() is only resolved when console.php route file is empty, otherwise it only lists (and processes) schedule from console.php and ignores ->withSchedule().