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

How to integrate Sentry in NestJS - DEV Community

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

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

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

php - vendor class not found in laravel - Stack Overflow

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

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

How to report Sentry exceptions asynchronously in Laravel? · Issue

라라벨 Laravel] PHP Fatal error: Uncaught ReflectionException

CS0234 errors on all views after creating new .NET ASP MVC project