When * DO * we show StackTraces on production systems

In what specific situation is it normal (or even recommended) to introduce StackTrace to end users in their user interface in the production system .

There are many websites and SO articles where people ask if they should show StackTraces to the end user. No wonder the answers are loud No! .

For instance:

• Java: what information in the error stack trace do we usually don’t want to show to users?
• java: Using printStackTrace in a production environment
• Should I print an exception stack trace?
• When to record a stop loss for a caught exception

However, I recently had a conversation with another developer, where I spent a lot of time thinking about why stacks should not be passed to the user through the user interface. This discussion made me go back and return to one of my main (absolute) tenants - the user will never see the raw StackTrace in production.

I could not find a single convincing reason. Nevertheless, I am sure that there is a valid usecase, and I would like to either understand this or feel comfortable while continuing to keep my tenant absolute .