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

Dependency outdated / pinned - requires php-http/discovery below

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

How to report Sentry exceptions asynchronously in Laravel? · Issue

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

Errors not showing up in Sentry · Issue #137 · getsentry/sentry

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

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

routes - Laravel 8 JetStream BindingResolutionException Target

Fatal error: Uncaught Error: Class Normalizer not found in /usr

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

Spiral Framework: The Basics - Errors handling

Laravel - Issues view shows exceptions originating in Middleware

validation - Laravel MessageBag errors array is empty in view but