- 02 May, 2017 1 commit
-
-
xster authored
* Don’t automatically pod setup if the user never did it * fix/add test * rename getters
-
- 01 May, 2017 1 commit
-
-
xster authored
* Add cocoapods reason * s/native/iOS
-
- 26 Apr, 2017 1 commit
-
-
Todd Volkert authored
`adb` can sometimes hang, which will in turn hang the Dart isolate if we're using `Process.runSync()`. This changes many of the `Device` methods to return `Future<T>` in order to allow them to use the async process methods. A future change will add timeouts to the associated calls so that we can properly alert the user to the hung `adb` process. This is work towards #7102, #9567
-
- 09 Apr, 2017 1 commit
-
-
Devon Carew authored
-
- 31 Mar, 2017 1 commit
-
-
Chris Bracken authored
Xcode builds depend on the Python 'six' module. If not present, exit immediately with a useful error message. The six module is included in the system default Python installation. We perform this check in case a custom Python install has higher priority on $PATH; e.g., due to a Homebrew or MacPorts installation. This extracts an existing doctor check to use it during the build step as well.
-
- 29 Mar, 2017 1 commit
-
-
Ian Hickson authored
-
- 27 Mar, 2017 2 commits
-
-
Jakob Andersen authored
-
Jakob Andersen authored
The very first time `pod install` is invoked, CocoaPods downloads the master spec repository, which takes quite a while. Before this change, the build appeared to have stalled. With this change, at least the spinner is moving. Added `pod setup` to the install instructions for CocoaPods, so the spec repo is downloaded while setting up Flutter, instead of during the first build.
-
- 16 Mar, 2017 1 commit
-
-
Jakob Andersen authored
* Only run pod install if CocoaPods v1.0.0 or greater is installed. Avoid issues with older versions of CocoaPods breaking the build. Users who genuinely use older versions of CocoaPods will have to run pod install manually when required.
-
- 10 Mar, 2017 4 commits
-
-
Todd Volkert authored
(follow-on to #8698)
-
Jakob Andersen authored
* Revert "Eliminate CocoaPods install step (#8694)" This reverts commit f4a13bc7. If the developer is relying on CocoaPods and hasn't done a pod install, we will do it for them. This is needed for a smooth native plugin experience, similar to what Gradle is doing on the Android side. There's no hard dependency on CocoaPods. We only run pod install if the project uses CocoaPods, so developers are still free to use alternatives if they prefer (and if they don't want to use native plugins). Fixes #8685 Fixes #8657 Fixes #8526 * Require CocoaPods 1.0.0 or newer. And make sure we don't get a crash if running `pod install` fails. * Address review feedback
-
Chris Bracken authored
This avoids unintentionally installing an older version if the developer's homebrew installation is out-of-date.
-
Chris Bracken authored
If the developer is relying on CocoaPods and hasn't done a pod install, they'll get a build failure indicating the issue. This also avoids a hard dependency on CocoaPods in the tool and allows developers to customize their Xcode steps to use alternatives such as Carthage if they prefer.
-
- 09 Mar, 2017 1 commit
-
-
Chris Bracken authored
As of the latest Xcode versions, the latest published libimobiledevice is out-of-date and build from HEAD is required. This fixes two bugs: 1. Update initial install instructions to add --HEAD flag. 2. Update uninstall, reinstall instructions to include --ignore-dependencies flag, since other brew formulae depend on libimobiledevice.
-
- 08 Mar, 2017 2 commits
-
-
Chris Bracken authored
This is consistent with the rest of the iOS toolchain.
-
Jakob Andersen authored
Since iOS builds are CocoaPods enabled by default, we should make sure to run `pod install` to get pods wired up before building the app. Also added a check to `flutter doctor` to verify CocoaPods is installed. I'm passing FLUTTER_FRAMEWORK_DIR to the `pod install` command, so we can have the app's Podfile link in Flutter.framework as a pod instead of having to copy it over in xcode_backend.sh.
-
- 07 Mar, 2017 1 commit
-
-
John McCutchan authored
* Request the user upgrade if the Android SDK version is 24 * Update android_sdk_test.dart * Update android_sdk.dart
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 28 Feb, 2017 1 commit
-
-
Devon Carew authored
* fix a doctor check for webstorm * fix a missing reference
-
- 15 Feb, 2017 1 commit
-
-
Chris Bracken authored
If a developer has installed the Xcode command-line tools, then later installs Xcode, they may need to run xcode-select to update the path of the command-line tools to that of the new installation.
-
- 09 Feb, 2017 2 commits
-
-
Chris Bracken authored
* Fix potential NPE in iOS doctor check In case Xcode is not installed, the xcode-select path may be null. * fixup! Fix potential NPE in iOS doctor check
-
Chris Bracken authored
If the developer has only installed the Xcode command-line tools, xcode-select and some other tools may be present, but xcodebuild will be missing. In this case, output a slightly improved message indicating that the installation is incomplete rather than missing.
-
- 08 Feb, 2017 1 commit
-
-
Chris Bracken authored
Differentiate between the not-installed and the out-of-date scenario.
-
- 02 Feb, 2017 3 commits
-
-
Chris Bracken authored
* Add doctor check for Python 'six' module Required as part of Xcode lldb module. In all likelihood, if we encounter this situation, the developer is using a custom Python install (e.g., via MacPorts or Homebrew).
-
Chris Bracken authored
ios-deploy -h/--help returns a non-zero exit code.
-
Chris Bracken authored
Ref: https://developer.apple.com/xcode/
-
- 01 Feb, 2017 2 commits
-
-
Chris Bracken authored
-
Chris Bracken authored
Also emits the version information in flutter doctor output. ios-deploy > 1.9.0 is required to deploy to iOS devices.
-
- 26 Jan, 2017 1 commit
-
-
Todd Volkert authored
-
- 09 Jan, 2017 1 commit
-
-
Todd Volkert authored
This ensures that accidental usages of dart:io's file API don't creep in over time.
-
- 12 Oct, 2016 1 commit
-
-
Chris Bracken authored
Previously, overall status was reported as good if Xcode and homebrew were installed, even if there were issues with either of the tools. We now report partial status if we detect issues with either installation.
-
- 28 Sep, 2016 1 commit
-
-
Chris Bracken authored
libimobiledevice 1.2.0 is incompatible with Xcode >= 8.0. Since the libimobiledevice tools don't include a --version flag, check for valid exit code on running idevicename, if an iOS device is connected.
-
- 01 Sep, 2016 1 commit
-
-
Dan Rubel authored
* show device list in flutter doctor output fixes https://github.com/flutter/flutter/issues/5625
-
- 24 Mar, 2016 2 commits
-
-
Devon Carew authored
-
Devon Carew authored
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 03 Mar, 2016 1 commit
-
-
Devon Carew authored
-
- 23 Feb, 2016 1 commit
-
-
Devon Carew authored
-
- 22 Feb, 2016 1 commit
-
-
Chinmay Garde authored
-
- 21 Feb, 2016 1 commit
-
-
Devon Carew authored
-