Component used: Fragment Version used: 1.4.0-alpha01

The Fragment StrictMode outputs to the log when you use penaltyLog() or penaltyDeath(). While these print the Violation class name and the stack trace, they don't provide useful structured information that would help developers figure out the cause of the exception from only the log message.

Building on top of b/187871150, each Violation should use what structured information it has access to in order to override the exception message with a more useful, pre-formatted log message.

We should still keep the currently used 'Policy violation in $fragmentName' message (as the exception message will be included in the output of the violation as the Exception parameter to the Log call.