Webhooks Attribute not found

[AlbertoSinigaglia]

when using Route::webhooks('...', '...') i get an error like:
InvalidArgumentException Attribute [webhooks] does not exist.
and in the stack trace, the error is thrown on the web.php file

[AlbertoSinigaglia]

my fault, it was Laravel 6.0 that cache package and service, removed the files and works fine

[vinayaWD]

@AlbertoSinigaglia Which cache package were you deleted?

[LouisCharles70]

I didn't understand how you solved the problem ? I have the same problem and doing "php artisan cache:clear" didn't solve the problem

[AlbertoSinigaglia]

I didn't understand how you solved the problem ? I have the same problem and doing "php artisan cache:clear" didn't solve the problem

If I don’t remember wrong, I’ve just runphp artisan route:clear and php artisan cache:clear

[AlbertoSinigaglia]

@AlbertoSinigaglia Which cache package were you deleted?

Sorry for being late, just answered

[kalnode]

If you come across the error "Attribute [webhooks] does not exist"... and you've been working in other branches with different composer configs, you may need to simply run "composer install" again to make sure the library is actually installed. Your config/migrations/etc should still be in place.

[hamza-saqib]

if it is cache issue then why I am getting this I just clone repo and run composer install and i got this same error ? i am using webbook client and and server package both. and using php 7
also i'm getting same error while running php artisan route:clear

[hondaman900]

Has anyone resolved this one? I'm on a Forger server, and running either php artisan cache:clear or php artisan route:clear commands fail, but returning this error:

In RouteRegistrar.php line 92:
  Attribute [stripeWebhooks] does not exist.

Not sure what to do next and my site is broken.

[hondaman900]

FWIW, turns out that for me it was Composer running out of memory when installing a new package. Creating a new composer.lock on my local dev (using composer update) and then committing that to the live server (after much tweaking to resolve Git sync issues) fixed the issue.