Open mertaydin opened 1 week ago
Hi @mertaydin
Can you please confirm that you have followed the documentation for configuring the logger and ensured correct binding to Psr\Log\LoggerInterface
? This will eliminate the reliance on the deprecated Illuminate\Contracts\Logging\Log interface
, which I believe is what was causing the issue.
For convenience you can find those docs here: https://docs.bugsnag.com/platforms/php/laravel/#laravel-5-6
Yes, I did everything according to documentation. I don't have any problem with bugsnag. But I think problem is unresolved namespace which was found by ide-helper package. It's scanning all classes for ide helper for autocompletion.
Hi @mertaydin,
To help us investigate this further, are you able to provide your full BugSnag configuration, along with your full composer.json
file? Or even better, would you be able to provide a stripped down example app that reproduces this?
If you are concerned about sharing these files publicly then please feel free to reach out to us via support@bugsnag.com.
Describe the bug
When you use laravel-bugsnag package with barryvdh/laravel-ide-helper, if you run
command giving this error.
Error messages:
``` laravel.EMERGENCY: Unable to create configured logger. Using emergency logger. {"exception":"[object] (ReflectionException(code: 0): Class 'Illuminate\\Contracts\\Logging\\Log' not found. ```Because of in
file's
namespace definition
Steps to reproduce
Environment