Routes cannot be cached in Starter Kits with Fortify, when Login route paths are not `/login`

[studnitz]

Laravel Version

12.0

PHP Version

8.4.0

Database Driver & Version

No response

Description

When running php artisan route:cache on a freshly installed Vue starter kit with Fortify, it fails when changing the Login route.

This is because both Fortify and the Auth login route do the assignment. When they have the same route path, this is apparently not a problem and the last one wins. But when you change the route path it fails:

  LogicException 

  Unable to prepare route [a/login] for serialization. Another route has already been assigned name [login].

Steps To Reproduce

• Install Laravel Vue Starter Kit with Auth scaffolding
• Open routes/auth.php
• Run php artisan route:cache, this should work
• Change Route::get('/login') to Route::get('/a/login')
• Run php artisan route:cache, this now fails.

[CreareWorks]

@studnitz

[ Investigation Result]

Hello. I tried to reproduce this issue on a fresh Laravel 12 installation.

I found that the latest version of Laravel Breeze no longer uses Laravel Fortify for its backend. Because Fortify is no longer present, the route name conflict described in this issue does not occur, and php artisan route:cache works correctly even after changing the login path.

It seems this issue has been resolved due to the architectural changes in recent Laravel versions. This issue can probably be closed.

Environment:

Laravel Framework: v12.32.5

Laravel Breeze: v2.3.8

---

composer show laravel/framework laravel/fortify

In VersionParser.php line 521:
                                                                                                
  Could not parse version constraint laravel/fortify: Invalid version string "laravel/fortify"  
                                                                                                

show [--all] [--locked] [-i|--installed] [-p|--platform] [-a|--available] [-s|--self] [-N|--name-only] [-P|--path] [-t|--tree] [-l|--latest] [-o|--outdated] [--ignore IGNORE] [-M|--major-only] [-m|--minor-only] [--patch-only] [-A|--sort-by-age] [-D|--direct] [--strict] [-f|--format FORMAT] [--no-dev] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<package> [<version>]]

[crynobone]

@CreareWorks Breeze never rely on Fortify.

[CreareWorks]

@CreareWorks Breeze never rely on Fortify.

Thank you, @crynobone, for the clarification. That makes perfect sense.

The original issue description mentioned a generic "Vue Starter Kit with Auth scaffolding," which is why I initially tested with Laravel Breeze.

As you confirmed, the issue doesn't affect Breeze. It seems highly likely that this bug is specific to Laravel Jetstream, since it relies on Fortify.

I will now set up a new project using Jetstream with Inertia (Vue) to try and reproduce it. I'll report my findings back here.

[CreareWorks]

Follow-up: I've now tested this with a fresh installation of Laravel Jetstream + Inertia.

I was unable to reproduce the issue on my end. This could be due to an error in my method, or it's also possible the issue has been resolved in a recent update to the framework or Fortify.

I hope these findings are helpful for triaging this issue.

My Environment:

• Laravel Framework: v12.32.5
• Laravel Jetstream: v5.3.8
• Laravel Fortify: v1.31.1

[ibrunotome]

@CreareWorks

• git clone https://github.com/laravel/vue-starter-kit
• cd vue-starter-kit
• composer i
• edit in routes/auth.php from /login to /auth/login
• php artisan route:cache

= broke, no breeze, no jetstream, just starker kits as issue mentioned.

[CreareWorks]

Thank you, @ibrunotome, for the clarification and for pointing to the correct repository. My apologies for the confusion my previous comments may have caused.

I had misinterpreted the original report and focused my investigation on the modern starter kits like Breeze and Jetstream. It's clear now that the issue is specific to the legacy laravel/vue-starter-kit.

I will now follow the steps you've provided to reproduce the issue with the correct starter kit and will report back here with my findings.

[CreareWorks]

Thank you, @ibrunotome, for the clarification and for pointing to the correct repository. My apologies for the confusion my previous comments may have caused.

I had misinterpreted the original report and focused my investigation on the modern starter kits like Breeze and Jetstream. It's clear now that the issue is specific to the legacy laravel/vue-starter-kit.

I will now follow the steps you've provided to reproduce the issue with the correct starter kit and will report back here with my findings.

 php artisan route:cache

   INFO  Routes cached successfully.  

oshimayota@HajimariYotaOshima vue-starter-kit % php artisan route:cache

   LogicException 

  Unable to prepare route [a/login] for serialization. Another route has already been assigned name [login].

  at vendor/laravel/framework/src/Illuminate/Routing/AbstractRouteCollection.php:248
    244▕             $route->name($this->generateRouteName());
    245▕ 
    246▕             $this->add($route);
    247▕         } elseif (! is_null($symfonyRoutes->get($name))) {
  ➜ 248▕             throw new LogicException("Unable to prepare route [{$route->uri}] for serialization. Another route has already been assigned name [{$name}].");
    249▕         }
    250▕ 
    251▕         $symfonyRoutes->add($route->getName(), $route->toSymfonyRoute());
    252▕ 

      +19 vendor frames 

  20  artisan:16
      Illuminate\Foundation\Application::handleCommand(Object(Symfony\Component\Console\Input\ArgvInput))

[CreareWorks]

Thank you again, @ibrunotome, (@crynobone, @studnitz). Your comment pointing to the laravel/vue-starter-kit was the key to solving this.

After a deep investigation, my findings suggest this may not be a bug in the Fortify package itself, but perhaps a configuration issue within the laravel/vue-starter-kit project.

The conflict can be resolved by setting 'views' => false in config/fortify.php. This makes sense, as Fortify is designed as a "headless" backend, and this starter kit provides its own UI. It aligns with the design philosophy of separating the data-providing backend from the frontend.

This leads to a question for the maintainers on the desired path forward:

Is the intended solution for users to set 'views' => false in their config? If so, this could be considered a configuration issue within the starter kit, and this issue could be closed.

Or, should Fortify itself be modified to handle this conflict gracefully without requiring a config change? This would likely involve finding a robust way to make checks like ! Route::has('login') work reliably during the route:cache command.

I am happy to investigate and create a PR for the second approach if the team prefers that direction. Please let me know your thoughts.

[crynobone]

This should be fixed in the latest vue-starter-kit