1. 03 Jan, 2019 1 commit
  2. 19 Dec, 2018 1 commit
  3. 20 Nov, 2018 1 commit
  4. 07 Nov, 2018 1 commit
  5. 05 Nov, 2018 1 commit
  6. 19 Sep, 2018 1 commit
  7. 12 Sep, 2018 1 commit
  8. 05 Sep, 2018 1 commit
    • tonyzhao1's avatar
      Create categories for doctor validators (#20758) · 58d98ce3
      tonyzhao1 authored
      * First step in Flutter Doctor refactor. Assigns categories to all validators.
      
      * Revert "Roll engine e54bc4ea1832..a84b210b3d26 (6 commits) (#20453)"
      
      This reverts commit 05c2880a.
      
      * Split iOS and Android workflows into workflow and validator classes.
      
      * Change ValidatorCategory to handle standalone validators that share a
      category (e.g. IntelliJ).
      
      Also make Android Studio and Android toolchain use separate categories.
      
      At this stage, flutter doctor output matches what it was previously.
      (The summary() method itself has not yet been changed )
      
      * Change doctor summary code to support validator categories.
      
      Output is still unchanged.
      
      * Handle small formatting issues.
      
      * Flip Flutter category's isGroup field to false until it's actually
      needed.
      
      * Revert auto-generated formatting changes to keep those lines from
      muddying the pull.
      
      * Small fixes pointed out by analyzer.
      
      * Properly fix analyzer issues around const constructors.
      
      * Small changes to address comments.
      
      * Add tests to verify grouped validator behavior and validationtype
      merging.
      
      * Update doctor.dart
      
      * Add comments for clarification.
      58d98ce3
  9. 12 Jul, 2018 1 commit
    • Chris Bracken's avatar
      Push /usr/bin to front of PATH for ios-deploy runs (#19281) · 379a2d56
      Chris Bracken authored
      ios-deploy relies on LLDB.framework, which relies on /usr/bin/python and
      the 'six' module that's installed on the system. However, it appears to
      use the first version of Python on PATH, rather than explicitly
      specifying the system install.  If a user has a custom install of Python
      (e.g., via Homebrew or MacPorts) ahead of the system Python on their
      PATH, LLDB.framework will pick up that version instead. If the user
      hasn't installed the 'six' module, ios-deploy will fail with a
      relatively cryptic error message.
      
      This patch pushes /usr/bin to the front of PATH for the duration of the
      ios-deploy run to avoid this scenario.
      
      This patch also removes checks for package six.
      
      Neither Flutter nor any of its direct dependencies/tooling relies on
      package six. ios-deploy depends on LLDB.framework (included with Xcode),
      which relies on a Python script that imports this package but uses
      whichever Python is at the front of the path. Flutter now invokes
      ios-deploy with a PATH with /usr/bin forced to the front in order to
      avoid this problem.
      
      We could have retained the check out of paranoia, but this seems
      unnecessary since it's entirely possible LLDB.framework may one day drop
      this dependency, in which case I'd expect the base system install of
      Python would likely drop it as well.
      379a2d56
  10. 31 May, 2018 1 commit
  11. 09 May, 2018 2 commits
  12. 08 May, 2018 1 commit
  13. 04 May, 2018 2 commits
  14. 30 Apr, 2018 2 commits
  15. 04 Apr, 2018 1 commit
  16. 28 Mar, 2018 1 commit
  17. 17 Mar, 2018 1 commit
  18. 07 Mar, 2018 1 commit
  19. 19 Feb, 2018 1 commit
  20. 19 Oct, 2017 1 commit
    • Chris Bracken's avatar
      Improve libimobiledevice doctor messages (#12633) · e965b692
      Chris Bracken authored
      The libimobiledevice suite of tools do not include version information.
      A simple way to verify they meet our version requirements is to run
      idevice_id -l, which will fail when older versions are run against iOS
      devices with newer versions of iOS installed.
      
      Unfortunately, idevice_id -l will also fail when libimobiledevice is up
      to date, but the attached devices have never been paired with the host
      machine in Xcode.
      
      This patch updates the error message to help guide the user in such
      situations.
      e965b692
  21. 28 Sep, 2017 1 commit
  22. 05 Sep, 2017 2 commits
  23. 01 Aug, 2017 1 commit
  24. 13 Jul, 2017 1 commit
    • xster's avatar
      Create Podfile dynamically part 1 (#11101) · 6a49419b
      xster authored
      * start
      
      * with create
      
      * refactor cocoapod code, add tests
      
      * fix tests
      
      * throw when cocoapod missing
      
      * obj-c projects don’t use use_framework!
      6a49419b
  25. 29 Jun, 2017 1 commit
  26. 16 Jun, 2017 3 commits
  27. 15 Jun, 2017 1 commit
  28. 02 Jun, 2017 1 commit
  29. 31 May, 2017 2 commits
    • Chris Bracken's avatar
      Clean up ideviceinstaller doctor messages (#10408) · 9c502cba
      Chris Bracken authored
      Eliminates nearly-duplicate install instructions for libimobiledevice,
      ideviceinstaller.
      
      Since ideviceinstaller depends on libimobiledevice, it's almost certain
      that if libimobiledevice isn't installed, or needs updating, so does
      ideviceinstaller.
      9c502cba
    • Chris Bracken's avatar
      Clarify libimobiledevice doctor check message (#10406) · 479e533b
      Chris Bracken authored
      This message will be emitted both when libimobiledevice requires
      updating, or when it has not yet been installed.
      
      It's also not specifically the version of Xcode that it's incompatible
      with, it's the lockdownd daemon, which is actually more closely tied to
      iTunes.
      479e533b
  30. 23 May, 2017 1 commit
  31. 22 May, 2017 2 commits
  32. 02 May, 2017 1 commit