Closed ideadx closed 9 years ago
Can you give it a try now? Let me know if it still happens—if it does (50/50) I’ll verify the psr-0 loader tomorrow and remove the classmap entries.
Also please ensure you’re using the latest version of composer with composer self update
On Jun 28, 2015, at 8:00 PM, Star18bit notifications@github.com wrote:
When running composer update: Ambiguous class resolution, "J42\LaravelFirebase\LaravelFirebaseServiceProvider" was found in both "/Users/xx/Sites/whipitseeder/vendor/j42/laravel-firebase/src/j42/LaravelFirebase/LaravelFirebaseServiceProvider.php" and "/Users/xx/Sites/whipitseeder/vendor/j42/laravel-firebase/src/j42/LaravelFirebase/LaravelFirebaseServiceProvider.php", the first will be used.
— Reply to this email directly or view it on GitHub .
@j42 All good now. Thank you. :+1:
When running composer update: Ambiguous class resolution, "J42\LaravelFirebase\LaravelFirebaseServiceProvider" was found in both "/Users/xx/Sites/project/vendor/j42/laravel-firebase/src/j42/LaravelFirebase/LaravelFirebaseServiceProvider.php" and "/Users/xx/Sites/project/vendor/j42/laravel-firebase/src/j42/LaravelFirebase/LaravelFirebaseServiceProvider.php", the first will be used.