- 29 Sep, 2019 2 commits
-
- 28 Sep, 2019 1 commit
-
-
liyuqian authored
This reverts commit f1e7fe81. This fix is in https://github.com/flutter/packages/pull/39
-
- 26 Sep, 2019 2 commits
-
-
Jonah Williams authored
-
liyuqian authored
This reverts commit 652be88e. This fix is in https://github.com/flutter/packages/pull/37
-
- 25 Sep, 2019 4 commits
-
-
Jonah Williams authored
-
Emmanuel Garcia authored
-
Jonah Williams authored
-
Jonah Williams authored
-
- 24 Sep, 2019 1 commit
-
-
Jonah Williams authored
-
- 19 Sep, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
Alexandre Ardhuin authored
-
- 17 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 16 Sep, 2019 2 commits
-
-
liyuqian authored
For https://github.com/flutter/flutter/issues/33899 Test added: - simple_animation_perf_ios Test modified: - backdrop_filter_perf_ios__timeline_summary We'll add the CPU/GPU measurement to more iOS tests once it's proven to be non-flaky.
- 11 Sep, 2019 2 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
-
- 09 Sep, 2019 1 commit
-
-
Todd Volkert authored
It was hitting the global devicelab 15 minute timeout.
-
- 30 Aug, 2019 3 commits
-
-
Christopher Fujino authored
This reverts commit 61eab16c.
-
Christopher Fujino authored
This reverts commit 8ec2c582.
-
Christopher Fujino authored
-
- 29 Aug, 2019 2 commits
-
-
Phil Quitslund authored
* migrate from slow async io calls
-
Jonah Williams authored
-
- 26 Aug, 2019 1 commit
-
-
Collin Jackson authored
* Fix plugin template * Add test of plugin template working
-
- 20 Aug, 2019 1 commit
-
-
Christopher Fujino authored
-
- 07 Aug, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 31 Jul, 2019 1 commit
-
-
liyuqian authored
This relands https://github.com/flutter/flutter/pull/35297 The followings have been done to fix the broken tests: 1. Add `didSendFirstFrameRasterizedEvent` extension and its tests 2. Wait for `didSendFirstFrameRasterizedEvent` instead of `didSendFirstFrameEvent` during start up tests 3. Mark missed (probably newly added) start up tests as flaky
-
- 30 Jul, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 26 Jul, 2019 3 commits
-
-
Jonah Williams authored
This reverts commit 68fc7231.
-
Jason Simmons authored
-
liyuqian authored
This should fix https://github.com/flutter/flutter/issues/31442 and https://github.com/flutter/flutter/issues/34867
-
- 24 Jul, 2019 1 commit
-
-
Matt Carroll authored
-
- 23 Jul, 2019 5 commits
-
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Emmanuel Garcia authored
This reverts commit 11460b83.
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Jonah Williams authored
-
Jonah Williams authored
-
- 22 Jul, 2019 1 commit
-
-
Ian Hickson authored
-
- 18 Jul, 2019 1 commit
-
-
Todd Volkert authored
This is the first step in getting esoteric devices wired up to device lab to ensure that we can at least start Flutter apps in profile mode on such devices. https://github.com/flutter/flutter/issues/35838
-