1. 18 Sep, 2018 3 commits
    • Alexander Markov's avatar
    • Chris Bracken's avatar
      Revert "Use Xcode legacy build system for iOS builds (#21901)" (#21966) · 4c045e79
      Chris Bracken authored
      This caused issues for projects without an Xcode workspace. Almost all
      Flutter projects in the wild will have a workspace, but this patch needs
      to add a check to catch any that lack one.
      
      This reverts commit 021f472e.
      4c045e79
    • Chris Bracken's avatar
      Use Xcode legacy build system for iOS builds (#21901) · 021f472e
      Chris Bracken authored
      Xcode 10 introduces a new build system which includes stricter checks on
      duplicate build outputs.
      
      When plugins are in use, there are two competing build actions that copy
      Flutter.framework into the build application Frameworks directory:
      
        1. The Embed Frameworks build phase for the Runner project
        2. The [CP] Embed Pods Frameworks build phase that pod install creates
           in the project.
      
      Item (1) is there to ensure the framework is copied into the built app
      in the case where there are no plugins (and therefore no CocoaPods
      integration in the Xcode project). Item (2) is there because Flutter's
      podspec declares Flutter.framework as a vended_framework, and CocoaPods
      automatically adds a copy step for each such vended_framework in the
      transitive closure of CocoaPods dependencies.
      
      As an immediate fix, we opt back into the build system used by Xcode 9
      and earlier. Longer term, we need to update our templates and
      flutter_tools to correctly handle this situation.
      
      See: https://github.com/flutter/flutter/issues/20685
      021f472e
  2. 17 Sep, 2018 4 commits
  3. 16 Sep, 2018 2 commits
  4. 14 Sep, 2018 12 commits
  5. 13 Sep, 2018 7 commits
  6. 12 Sep, 2018 12 commits