Inconsistent Gradle warning visibility between Flutter IDE Run and command‑line builds

When diagnosing a failed Flutter Android deployment, developers often compare the output from the IDE’s Run button with that from the command line to locate Gradle‑related issues.

Observations show that certain Gradle warnings—such as version‑compatibility notices or unresolved dependency hints—are visible in the verbose CLI logs but disappear from the IDE console, making it harder to spot the root cause without switching to a terminal.

This discrepancy raises questions about how the IDE captures and forwards Gradle’s stderr/stdout streams and whether any filtering occurs intentionally or as a side effect of the launch configuration.

What specific Gradle messages are suppressed in the IDE Run console?

Is the suppression configurable through Flutter or IDE settings?

How can developers ensure consistent visibility of warnings across both execution paths?