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

Missing Issues · Issue #252 · getsentry/sentry-laravel · GitHub

How To Fix No application encryption key has been specified error

Next.js middleware support · Issue #4206 · getsentry/sentry

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

Laravel - Issues view shows exceptions originating in Middleware

php - Cannot use object of type stdClass as array in laravel API

php - Cannot use object of type stdClass as array using laravel

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

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

Variable values are not shown in issue view - SDKs - #sentry