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

validation - Laravel MessageBag errors array is empty in view but

php - vendor class not found in laravel - Stack Overflow

Laravel - Issues view shows exceptions originating in Middleware

安装好后报错Class view does not exist in, Laravel

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

Errors not caught by Laravel exception handler are still sent to

Sentry JavaScript SDK `ignoreErrors` option not documented · Issue

Uncaught exception 'ReflectionException' with message 'Class

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

Laravel middleware 'except' rule not working - Stack Overflow

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

Sentry + Laravel: A Powerful Duo for Error Tracking and Debugging

Sentry for Laravel - Poovarasu - Medium

Laravel error - Uncaught exception 'ReflectionException' with

Sentry for Laravel - Poovarasu - Medium