Skip to content

Make flutter analyze --suggestion provide suggested versions in all error messages #167931

Open

Description

@reidbaker

flutter analyze --suggestions can tell users when their versions are incompatible but not what the right version is.

Multiple users have told me as an example that https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin is too many words and they will continue to be frustrated rather than read the documenation.

The fallback solution seems to be to run flutter create then diff the gradle files. This happens even with full time flutter contributors.

Adding to this confusion is that the newest of all versions fail the compatibility check even though the builds appear to work even at scale. Kotlin full support seems like it is limited to a couple of AGP versions older than the most recent which we might warn on but not suggest downgrading.

Activity

  1. added
    team-androidOwned by Android platform team
    P2Important issues not at the top of the work list
    platform-androidAndroid applications specifically
    on Apr 28, 2025
  2. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Sep 2, 2025
  3. flutter-triage-bot commented on Sep 2, 2025

    @flutter-triage-bot

    This issue is assigned to @jesswrd but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  4. flutter-triage-bot commented on Nov 22, 2025

    @flutter-triage-bot

    This issue was assigned to @jesswrd but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

  5. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Nov 22, 2025
  6. self-assigned this
    on Nov 25, 2025
  7. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Apr 1, 2026
  8. flutter-triage-bot commented on Apr 1, 2026

    @flutter-triage-bot

    This issue is assigned to @jesswrd but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  9. flutter-triage-bot commented on Jun 18, 2026

    @flutter-triage-bot

    This issue was assigned to @jesswrd but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

  10. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Jun 18, 2026
  11. added a commit that references this issue on Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listplatform-androidAndroid applications specificallyteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions