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

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

Dependency outdated / pinned - requires php-http/discovery below

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

How to integrate Sentry in NestJS - DEV Community

Sentry for Laravel - Poovarasu - Medium

Sentry JavaScript SDK `ignoreErrors` option not documented · Issue

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

php - vendor class not found in laravel - Stack Overflow

How to integrate Sentry in NestJS - DEV Community

Laravel middleware 'except' rule not working - Stack Overflow

Spiral Framework: The Basics - Errors handling

Unexpected exception when instantiating class. · Issue #795

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

Sentry exceptions are not showing when php artisan sentry:test

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