Laravel - Issues view shows exceptions originating in Middleware instead of the correct class - SDKs - #sentry

Hello all, I have an existing mobile-app API based on Laravel 5.2. I make a request against an endpoint which passes the request through several Middleware classes after which it arrives at a controller that sends it to a service class that throws an exception. My problem is that instead of the Issues page in Sentry showing the exception as originating in the service class it shows it as originating in one of the Middleware classes (you’ll notice in the below pic that it seems all my exceptio

Errors not caught by Laravel exception handler are still sent to

Release tracking for commits. · Issue #426 · getsentry/sentry

How to integrate Sentry in NestJS - DEV Community

After upgrade to 1.7.7 clicking on any order in BO result in a

Bug missed_checkin in 3.6.0 · Issue #722 · getsentry/sentry

How to integrate Sentry in NestJS - DEV Community

After upgrade to 1.7.7 clicking on any order in BO result in a

How To Fix No application encryption key has been specified error

Laravel Sanctum: Access has been blocked by CORS policy: Response

Error when accessing /laravel-filemanager · Issue #516 · UniSharp

Errors not showing up in Sentry · Issue #137 · getsentry/sentry