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 getting grouped when they are the same from inside

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

Unable to view orders in back office - General topics - PrestaShop

php - Why do I get Missing configuration for public_key error on

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

Laravel error - Uncaught exception 'ReflectionException' with

Laravel middleware 'except' rule not working - Stack Overflow

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

Jens Segers - Laravel error logging with Sentry

How to integrate Sentry in NestJS - DEV Community

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