Skip to content

Android SDK 24 can lead to crashes with devices and Macs, but flutter tool says 24 is OK #7588

Closed

Description

@sethladd

We diagnosed a problem with crashing from device+flutter+mac. After the user upgraded to Android SDK 25, the crashes stopped. See #7332 (comment)

We might want to change flutter tool to prompt the user to upgrade to Android 25. Right now, flutter tool says 24 is OK.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Jan 23, 2017
  2. sethladd commented on Jan 31, 2017

    @sethladd
    ContributorAuthor

    I confirmed with our user that once he upgraded to Android SDK 25, his crashes went away.

    We recommend that flutter doctor suggest the user upgrade to 25.

    Are we aware of a reason to continue to prefer 24?

  3. sethladd commented on Jan 31, 2017

    @sethladd
    ContributorAuthor

    cc @abarth or @jason-simmons might know some background here...

  4. sethladd commented on Feb 8, 2017

    @sethladd
    ContributorAuthor

    Hi. This might help avoid issues for new users on macs. If this is easy, can we do this by/before March 8th ?

  5. abarth commented on Feb 8, 2017

    @abarth
    Contributor

    I'm not aware of any reason to prefer SDK 24.

  6. eseidelGoogle commented on Feb 8, 2017

    @eseidelGoogle
    Contributor

    Sounds like a simple fix to flutter doctor:
    https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/android/android_workflow.dart#L15
    Looks like we check a bunch of versions, but not sure we require one yet.

  7. modified the milestones: 1: Top Customer Requests, on Feb 17, 2017
  8. mit-mit commented on Feb 28, 2017

    @mit-mit
    Member

    @johnmccutchan are you looking at this one?

  9. removed
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Feb 28, 2017
  10. johnmccutchan commented on Feb 28, 2017

    @johnmccutchan
    Contributor
  11. github-actions commented on Sep 5, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  12. locked as resolved and limited conversation to collaborators on Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

t: flutter doctorProblem related to the "flutter doctor" tool

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions