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

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

Sentry for Laravel - Poovarasu - Medium

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

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

Bug missed_checkin in 3.6.0 · Issue #722 · getsentry/sentry

routes - Laravel 8 JetStream BindingResolutionException Target

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

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

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

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

asp.net core - model item passed into the ViewDataDictionary is of

라라벨 Laravel] PHP Fatal error: Uncaught ReflectionException