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

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

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

Sentry JavaScript SDK `ignoreErrors` option not documented · Issue

Laravel 8 Error Logging using Sentry

Two Sentry issues for one exception · Issue #261 · getsentry

SentryContext's middleware is not handled · Issue #299 · getsentry

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

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

Error when accessing /laravel-filemanager · Issue #516 · UniSharp