Skip to content

Conversation

@browner12
Copy link
Contributor

this command currently has 2 conditions it checks to try and activate the "channels" file in your /bootstrap/app.php. while this may cover a good chunk of users, it fails if the commands: named argument has been removed from the file.

this change adds an additional check to look for the ->withRouting() method call, which has a very high likelyhood of being in the file. placing it after the "commands" named argument is ideal because it maintains named argument order, but this is a good fallback.

if even this additional check fails, it now returns an error message to the user telling them they need to manually activate the broadcast routes in their /bootstrap/app.php file. this will helpfully avoid confusion if the automatic enabling fails.

this command currently has 2 conditions it checks to try and activate the "channels" file in your `/bootstrap/app.php`.  while this may cover a good chunk of users, it fails if the `commands:` named argument has been removed from the file.

this change adds an additional check to look for the `->withRouting()` method call, which has a *very* high likelyhood of being in the file. placing it after the "commands" named argument is ideal because it maintains named argument order, but this is a good fallback.

_if even this additional check fails_, it now returns an error message to the user telling them they need to manually activate the broadcast routes in their `/bootstrap/app.php` file. this will helpfully avoid confusion if the automatic enabling fails.
@taylorotwell taylorotwell merged commit f5d5c5a into laravel:12.x Nov 10, 2025
66 checks passed
@browner12 browner12 deleted the AB-broadcast-route-activation branch November 11, 2025 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants