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

Sentry exceptions are not showing when php artisan sentry:test

Variable values are not shown in issue view - SDKs - #sentry

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

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

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

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

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

Laravel middleware 'except' rule not working - Stack Overflow

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

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

unlabeled event> when reporting error from embedded webview - #sentry