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

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

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

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

Uncaught ReflectionException: Class env does not exist · Issue

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

validation - Laravel MessageBag errors array is empty in view but

라라벨 Laravel] PHP Fatal error: Uncaught ReflectionException

Sentry doesn't send exceptions · Issue #368 · getsentry/sentry

Target class [PostController] does not exist. - Amit Kumar - Medium

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

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

Laravel View Exists - Laravel News