- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 30 Aug, 2018 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 15 Aug, 2018 1 commit
-
-
Ian Hickson authored
* Upgrade everything except matcher. * Roll matcher (and test) * Adjust tests that depend on flutter:test directly to depend on a shim * Require use of package:test shim and remove other references to package:test
-
- 24 May, 2018 1 commit
-
-
Tim Neumann authored
-
- 19 Mar, 2018 1 commit
-
-
Matan Lurey authored
-
- 12 Mar, 2018 1 commit
-
-
Jason Simmons authored
-
- 12 Jan, 2018 1 commit
-
-
Chris Bracken authored
Apple encodes syslog entries using a 7-bit encoding where input UTF-8 bytes are encoded as follows: 1. 0x00 to 0x19: non-printing range. Some ignored, some encoded as <...>. 2. 0x20 to 0x7f: as-is, with the exception of 0x5c (backslash). 3. 0x5c (backslash): octal representation \134. 4. 0x80 to 0x9f: \M^x (using control-character notation for range 0x00 to 0x40). 5. 0xa0: octal representation \240. 6. 0xa1 to 0xf7: \M-x (where x is the input byte stripped of its high-order bit). 7. 0xf8 to 0xff: unused in 4-byte UTF-8. As there doesn't appear to be a system tool to decode these strings, we implement here in Dart. If we're unable to decode a string (e.g. decoding results in an invalid UTF-8 string), we fall back to emitting the log line as-is.
-
- 19 Dec, 2017 1 commit
-
-
Alan Russian authored
* Change async stubbing to use thenAnswer. Mockito now prohibits calling thenReturn with Futures and Streams. dart-lang/mockito#79 * Update all Mockito deps to 3.0.0. * Revert "Update all Mockito deps to 3.0.0." This reverts commit e8ab9d37c33d3d7fe384abde64ea5b4d72623c75. I did not correctly update the mockito dep, and there's no easy way to update to 3.0 alpha right now. * Change thenAnswer((_) => to thenAnswer((invocation) => * Add Invocation type to thenAnswer lambdas
-
- 07 Sep, 2017 2 commits
-
-
Chris Bracken authored
This was introduced to suppress libMobileGestalt noise originating from libsystem_asl.dylib. Commit 39680ebf suppresses all application log messages not originating from the app/engine iteself on iOS 10 and above. Since the log message in question is only emitted on devices running iOS >= 10.3.0, this blacklist no longer necessary.
-
Chris Bracken authored
On iOS 10 and above, suppress engine log messages from system components other than Flutter. This eliminates a large amount of keyboard/plugin related noise during edit-refresh development.
-
- 01 Sep, 2017 1 commit
-
-
Chris Bracken authored
This patch migrates iOS device listing from using Xcode instruments to using the libimobiledevice tools idevice_id and ideviceinfo. ideviceinfo was previously incompatible with iOS 11 physical devices; this has now been fixed. In 37bb5f13 flutter_tools migrated from libimobiledevice-based device listing on iOS to using Xcode instruments to work around the lack of support for iOS 11. Using instruments entails several downsides, including a significantly higher performance hit, and leaking hung DTServiceHub processes in certain cases when a simulator is running, necessitating workarounds in which we watched for, and cleaned up leaked DTServiceHub processes. This patch returns reverts the move to instruments now that it's no longer necessary.
-
- 31 Aug, 2017 1 commit
-
-
Alexandre Ardhuin authored
* upgrade to linter-0.1.35 * re-enable lint prefer_const_constructors * address review comments
-
- 23 Aug, 2017 1 commit
-
-
Chris Bracken authored
This patch supports basic filtering of log lines from physical iOS devices, similar to existing functionality for iOS simulator logging. This patch also suppresses the following two log messages which are emitted at app startup on iOS 10.3 devices: libMobileGestalt MobileGestaltSupport.m:153: pid 123 (Runner) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see <rdar://problem/11744455>)
-
- 19 Jun, 2017 1 commit
-
-
Chris Bracken authored
This reverts commit b2909a24. This resubmits the following patches: 1. Use Xcode instruments to list devices (#10801) Eliminates the dependency on idevice_id from libimobiledevice. Instead, uses Xcode built-in functionality. 2. Make device discovery asynchronous (#10803) Migrates DeviceDiscovery.devices and all device-specific lookup to be asynchronous.
-
- 17 Jun, 2017 2 commits
-
-
Chris Bracken authored
* Revert "Make device discovery asynchronous (#10803)" This reverts commit 972be9c8. * Revert "Use Xcode instruments to list devices (#10801)" This reverts commit 37bb5f13. This is to resolve a failure that looks related to a bad install of Xcode 8.0 on our build bots and should be reinstated when the infra issue is diagnosed and resolved. Instruments worked well when this was originally landed, and on the following commit, but started failing two commits after this originally landed. Manual invocation of instruments on the build host currently results in: ``` dyld: Library not loaded: @rpath/InstrumentsAnalysisCore.framework/Versions/A/InstrumentsAnalysisCore Referenced from: /Applications/Xcode8.0.app/Contents/Developer/usr/bin/instruments Reason: image not found Abort trap: 6 ``` It appears the /Applications/Xcode8.0.app/Contents/Applications directory (which contains Instruments) is missing on the host.
-
Chris Bracken authored
Migrates DeviceDiscovery.devices and all device-specific lookup to be asynchronous.
-
- 16 Jun, 2017 3 commits
-
-
Chris Bracken authored
Eliminates the dependency on idevice_id from libimobiledevice. Instead, uses Xcode built-in functionality.
-
Chris Bracken authored
Moves all remaining calls to tools that are part of the libimobiledevice suite of tools to the IMobileDevice class. This allows for better tracking of this dependency, and easier mocking in tests.
-
Chris Bracken authored
Extract out IMobileDevice class, move class to idevice_id, ideviceinfo (and eventually other libimobiledevice tools such as iproxy) behind this interface. Add tests for the case where libimobiledevice is not installed, the case where it returns no devices, and the case where it returns device IDs.
-
- 15 Jun, 2017 1 commit
-
-
Chris Bracken authored
-
- 12 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 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
-
- 10 Mar, 2017 2 commits
-
-
Todd Volkert authored
-
Todd Volkert authored
`all.dart` is no longer needed. Furthermore, it causes tests to be skipped, or to silently fail to run anything. Fixes #7941
-
- 28 Feb, 2017 1 commit
-
-
Yegor authored
-
- 17 Feb, 2017 1 commit
-
-
xster authored
* Support iOS screenshot 1/3 * Use path.join * use fs.path instead
-