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

Why Gradle Warnings Disappear in the IDE

The discrepancy in warning visibility occurs because the IDE Run button and the command-line interface (CLI) use different mechanisms to execute and capture Gradle output. When you run a build from the CLI, you are interacting directly with the Gradle wrapper, which streams stdout and stderr to your terminal. In contrast, IDEs like Android Studio and IntelliJ use the Gradle Tooling API.

The Tooling API captures build output as a structured event stream rather than a raw text stream. By default, the IDE filters this stream to prioritize task execution summaries and critical errors, often suppressing LIFECYCLE and INFO level messages. This includes deprecated API notices, version-compatibility warnings, and dependency resolution hints.

Likely Explanations vs. Confirmed Behaviors

Feature	CLI Behavior	IDE Run Console Behavior
Output Stream	Raw stdout/stderr	Filtered Tooling API events
Warning Mode	Honors --warning-mode	Often ignores CLI flags; uses internal filters
Log Level	Controlled by Gradle flags	Filtered by IDE's console settings

How to Ensure Consistent Visibility

To align the IDE output with the CLI, use the following methods depending on your environment:

1. Force Verbose Output via Flutter

If you are using the IDE's Run configuration, add the --verbose flag to the Additional run args field. This forces the Flutter tool to pass --info to Gradle, surfacing most suppressed warnings in the console.

2. Configure Gradle Global Logging

To make warnings persistent regardless of the caller, add the following to your android/gradle.properties file:

org.gradle.logging.level=WARN
org.gradle.warning.mode=all

3. Adjust IDE Console Settings (Android Studio 2024.1+)

• Right-click within the Run console window.
• Select Show all output (or similar visibility toggle) to disable the IDE's internal event filtering.

Verification Steps

To verify that the IDE is actually receiving the warnings (even if it isn't showing them), you can inspect the Gradle daemon log directly while the IDE build is running:

tail -f ~/.gradle/daemon/*/daemon-*.out

If the warnings appear in the daemon log but not in the IDE console, the issue is confirmed as IDE-level filtering.

Diagnostic Detail Needed: Which IDE and version are you using (e.g., Android Studio Hedgehog, VS Code)? Filtering behavior differs significantly between the IntelliJ-based Tooling API and the VS Code Flutter extension's process forwarding.