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

Errors not getting grouped when they are the same from inside

php - vendor class not found in laravel - Stack Overflow

Laravel 8 Error Logging using Sentry

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

Laravel - Issues view shows exceptions originating in Middleware

Laravel - Issues view shows exceptions originating in Middleware

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

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

Laravel middleware 'except' rule not working - Stack Overflow