No app crash logs since updating OS 15.7.2 to 26.1. How to fix?

Sorry, this was supposed to attach to my last:

What is interesting is that the EtreCheck install listing definitely misses some apps installed, including the app most of interest: Tinderbox. I aslo see RStudio and a few others are missing. I'm wondering if Tahoe added some new requirement on first run to 'register' in a way that wasn't needed before. If the app isn't seen as installed it *might* be a reason the OS might not let it write a crash log. There has to be some reason. The app of interest I've been using since 2003 across multiple iterations of OS X, / macOS, so it's not a 'my first app' sort of thing; the released app is very stable, my crashes are early beta tests of new features. There has to be some reason why these logs are getting written.

Since updating from macOS 15.7.2 to macOS 26.1, app crash logs are no longer generated—in user or system locations) not does the OS Crash Reporter dialog show after crashes.

The issue isn't a single app but a number of apps I have observed to crash but no crash log is generated. It feels like a permissions issue somewhere. The same apps, same crash under macOS 15.x generated logs.

I don't have time to do a ground up system rebuild (not do I have any exotic extensions, etc.). Basically, moving to Tahoe broke crash logging - how do I fix or even diagnose it. At present I have no repeatable crash scenarios I can use as a test (e.g. running console before to try and catch permissions error reports)

[Edited by Moderator]

For clarity, yes, I do know where crash logs live but as it seems you're unsure, the user location is at:

~/Library/Logs/DiagnosticReports

and the system location is at:

/Library/Logs/DiagnosticReports

Generally, application crash logs are found in the user Library location^† (above). Hang/high usage event logs were saved to the system location. I've been sending app crash logs to devs for decades which is why I'm quite familiar with where they live. :-)

EtreCheck Pro reports no relevant issues: I'd already checked this when I first spotted the problem and before posting here. This is a 2024 MBPro M4max so not short of cpu/RAM/space.

Indeed, the morning of the day I updated my MBPro OS to Tahoe (v26.1 - thread title is wrong but I can't correct it) I sent some app crash reports from the user location.

It wasn't until I had updated macOS from 15.7.2 to 26.1 that I noticed the same app crashes occurred but I couldn't find the crash logs nor was the OS crash reported dialog shown. At the time I had a crash in 15.7.2 that made a log and the same crash under 26.1 created no lot. Plus, I was tracking crashes in more than one app, so it isn't one 'rogue' app.

I can't find any thing in the console indicating an issue. The crashes I was tracking are now fixed. I guess I could ask one of the devs for an unfixed crasher I can replicate to try and crash with the Console running.

After much online digging, this is a known but not formally admitted OS bug . The best guess is some permissions were mangled during the OS upgrade. I've too much on to 'just' rebuild the OS and configure 100s of apps in the hope it might fix the issue. More constructively, I'd like to bear down on where the permissions may be at fault. Likely it's some plist or container permissions that need a fix.

So where best to look?

†. I do this often enough that my Mail apps' default location when additional attachments is the DiagnosticReports

The System Info / Logs has nothing app related (I checked each of the logs (top right list) in BBEdit. IORegistry log mentions one app of interest but not in any fashion indicating anything pertinent.

This is the end of the Etre Check Pro report, only cited apps appear to be macOS/Apple internal stuff.

Odd.