[cleanup] Provide a single way for detecting if a project is using AndroidX #40800

Activity

1. blasten

   added

   toolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.

   on Sep 19, 2019
2. escamoteur commented on Sep 19, 2019

   

   escamoteur

   on Sep 19, 2019

   Contributor

   More actions

   Maybe the Team understands what you mean, but could you elaborate what exactly the problem is?
3. escamoteur

   added

   waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter respondsThe Flutter team cannot make further progress on this issue until the original reporter responds

   on Sep 19, 2019
4. blasten commented on Sep 19, 2019

   

   blasten

   on Sep 19, 2019

   Author

   More actions

   The problem is that there are two ways of detecting if a project is using AndroidX, but the two ways belong to two different abstraction layers:

   • pubspec.yaml belongs to FlutterManifest.
   • gradle.properties belongs to AndroidProject.

   An AndroidProject instance doesn't know anything about FlutterManifest.
5. no-response

   removed

   waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter respondsThe Flutter team cannot make further progress on this issue until the original reporter responds

   on Sep 19, 2019
6. escamoteur commented on Sep 19, 2019

   

   escamoteur

   on Sep 19, 2019

   Contributor

   More actions

   You mean so that the App can access this information at runtime?
7. blasten commented on Sep 19, 2019

   

   blasten

   on Sep 19, 2019

   Author

   More actions

   You mean so that the App can access this information at runtime?

   The tool. This information is not exposed to the app at runtime.

   👍React with 👍1Reacted by Thomas Burkhart
8. escamoteur

   added

   c: proposalA detailed proposal for a change to FlutterA detailed proposal for a change to Flutter

   on Sep 19, 2019
9. blasten commented on Mar 10, 2020

   

   blasten

   on Mar 10, 2020

   Author

   More actions

   This is obsolete now.
10. blasten

    closed this as completedon Mar 10, 2020
11. lock commented on Apr 5, 2020

    

    lockBot

    on Apr 5, 2020

    More 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. lock

    locked and limited conversation to collaborators on Apr 5, 2020