1. 28 Feb, 2020 2 commits
  2. 27 Feb, 2020 2 commits
  3. 12 Feb, 2020 2 commits
  4. 11 Feb, 2020 1 commit
  5. 27 Jan, 2020 1 commit
  6. 17 Jan, 2020 1 commit
  7. 16 Jan, 2020 1 commit
  8. 13 Jan, 2020 1 commit
  9. 07 Jan, 2020 1 commit
  10. 06 Jan, 2020 1 commit
  11. 03 Jan, 2020 1 commit
  12. 13 Dec, 2019 2 commits
  13. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  14. 24 Nov, 2019 1 commit
  15. 01 Nov, 2019 1 commit
  16. 23 Oct, 2019 1 commit
  17. 22 Oct, 2019 2 commits
  18. 11 Oct, 2019 2 commits
  19. 08 Oct, 2019 1 commit
  20. 07 Oct, 2019 2 commits
  21. 06 Oct, 2019 1 commit
  22. 05 Oct, 2019 3 commits
  23. 03 Oct, 2019 1 commit
  24. 27 Sep, 2019 1 commit
  25. 16 Jul, 2019 2 commits
    • Christopher Fujino's avatar
    • sjindel-google's avatar
      Keep LLDB connection to iOS device alive while running from CLI. (#36194) · 5501a1c1
      sjindel-google authored
      ## Description
      
      Instead of detaching from the spawned App process on the device immediately, keep the LLDB client connection open (in autopilot mode) until the App quits or the server connection is lost.
      
      This replicates the behavior of Xcode, which also keeps a debugger attached to the App after launching it.
      
      ## Tests
      
      This change will be covered by all running benchmarks (which are launched via "flutter run"/"flutter drive"), and probably be covered by all tests as well.
      
      I also tested the workflow locally -- including cases where the App or Flutter CLI is terminated first.
      
      ## Breaking Change
      
      I don't believe this should introduce any breaking changes. The LLDB client automatically exits when the app dies or the device is disconnected, so there shouldn't even be any user-visible changes to the behavior of the tool (besides the output of "-v").
      5501a1c1
  26. 13 Jul, 2019 1 commit