- 08 Feb, 2021 1 commit
-
-
Jonah Williams authored
This reverts commit 8b6baae4.
-
- 04 Feb, 2021 1 commit
-
-
Jonah Williams authored
Our current top crasher is an unclear error when ProcessManager fails to resolve an executable path. To fix this, we'd like to being adjusting the process resolution logic and adding more instrumentation to track failures. In order to begin the process, the ProcessManager has been folded back into the flutter tool
-
- 28 Jan, 2021 1 commit
-
-
Jenn Magder authored
-
- 27 Jan, 2021 1 commit
-
-
Jonah Williams authored
* opt out the flutter tool * oops EOF * fix import * Update tool_backend.dart * Update daemon_client.dart * fix more
-
- 12 Oct, 2020 1 commit
-
-
Jonah Williams authored
Work towards #39925 Currently flutter run will uninstall and reinstall if the initial install fails and the APK was previously installed. Allow drive to share this same logic by moving it into installApp and out of startApp. This should reduce the occurrence of the error in the devicelab.
-
- 08 Jun, 2020 1 commit
-
-
Jenn Magder authored
-
- 20 May, 2020 1 commit
-
-
Jonah Williams authored
-
- 19 May, 2020 2 commits
-
-
Jonah Williams authored
This reverts commit 602d8baf.
-
Jonah Williams authored
-
- 10 Mar, 2020 1 commit
-
-
Jonah Williams authored
When the AndroidDevice checks for the current API version, it isn't handling a null response. While we can refuse to run on API levels that are unsupported, we should probably assume that a null response = lowest possible API level and allow these to run.
-