Laravel - Issues view shows exceptions originating in Middleware instead of the correct class

Hey Idan,

This should not be happening but I have an idea why it might.

This service and/or controller, are they not in the “regular” app path but in the vendor folder perhaps?

Sentry scopes error by code inside the app path and outside and I think it sees the origin of the error outside that app path.

It sets the app path based on the base_path() and excludes base_path() . '/vendor' by default.

This might be the issue?