-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing config file results in exception not being sent to Sentry #163
Comments
Okay, finally I found the problem. The problem is on the The simplest solution to solve this issue, instead set |
Okay good one, need to check when the merge config was introduced so we can implement it (still supporting 5.0 so need to be sure it was available then or add version switch for it). However, I do want to note that in the installation docs creating the config is mentioned and not as optional :) |
@stayallive Oh nice, my bad. I used Sentry since a long time ago, and I don't remember at that time, creating (publish) the config is mentioned in docs or not. And, the important thing, before this package introduce Fyi, as far as I know, publish config is always optional on Laravel package. So, maybe |
I agree, fixing this by 0d49fca |
Description:
The exception not being sent to the sentry. The problem actually happen on my production app with Laravel 5.6, using sentry-laravel version 0.9.*. Then, I decided to upgrade senty-laravel to 0.10.1. But, the issue still persist.
Finally, I try to use on fresh Laravel installation. But, the issue still.
Steps To Reproduce:
composer create-project laravel/laravel MyApp --prefer-dist
composer require sentry/sentry-laravel
SENTRY_LARAVEL_DSN
to.env
The text was updated successfully, but these errors were encountered: