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

Two Sentry issues for one exception · Issue #261 · getsentry

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

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

laravel-sentry Not working with auth middleware · Issue #308

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

Spiral Framework: The Basics - Errors handling

Target class [PostController] does not exist. - Amit Kumar - Medium

How to integrate Sentry in NestJS - DEV Community

Uncaught ReflectionException: Class env does not exist · Issue