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

Laravel middleware 'except' rule not working - Stack Overflow

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

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

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

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

Issues not tracking although `php artisan sentry:test` works fine

How to integrate Sentry in NestJS - DEV Community

Laravel View Exists - Laravel News

Sentry doesn't send exceptions · Issue #368 · getsentry/sentry