Removing composer.lock solved it for me. I had the same error during the event triggers after composer update.
I'm having the same issue, and removing composer.lock didn't work for me. Any hint?
One more thing. This happens when running composer update with "laravel/framework": "4.0." It seems to work properly on 4.1.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community