Stracktrace in_app directives sent properly but ignored in Sentry

[Aterniad]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

1. Sentry 25.9.0 / Laravel-Sentry 4.22.0
2. Configure in_app_include, e.g:

'in_app_include' => [base_path('vendor/custom_one'),],

4. Trigger any exception
5. Check sentry json before send:

# exception > values > stacktrace > frames > [{
"filename": "\/vendor\/custom_one\/File.php",
"lineno": 35,
"in_app": true,
"abs_path": "\/var\/www\/vendor\/custom_one/File.php",

Doesn't seem to be an SDK issue since "in_app" are sent

Expected Result

All frames starting with "/vendor/custom_one" are shown by default and have an extra "In App" label

Actual Result

Frames starting with "/vendor/custom_one" are hid by default, no "In App" label next to it

Product Area

Issues

Link

No response

DSN

No response

Version

25.9.0

[linear-code]

ENG-7093

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[shayna-ch]

Hi @Aterniad! Since your frame is being correctly sent as in-app on the client side, is it possible that you have server side stack trace rules that are overriding your SDK configuration?

You can check this by going to Project Settings → Issue Grouping → Stack Trace Rules, and look for any -app rules that could be applying to these frames.

[lobsterkatie]

You can also scroll down to the grouping info section at the bottom of the issue details page, find the frames in question (you may need to switch to the "All values" view), and it should tell you why they were marked out of app.

[Aterniad]

Hi @Aterniad! Since your frame is being correctly sent as in-app on the client side, is it possible that you have server side stack trace rules that are overriding your SDK configuration?

You can check this by going to Project Settings → Issue Grouping → Stack Trace Rules, and look for any -app rules that could be applying to these frames.

Thanks for pointing this out!
Though my rules were set by default over there, I've learned a docs a bit and set mine:

stack.abs_path:**/vendor/custom_one/** +app

That did a trick but I still kinda miss a point what caused Sentry to ignore in_app (had no breaking rules in grouping)