mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
4a65a76279
Reland https://github.com/flutter/flutter/pull/146558, reverted in https://github.com/flutter/flutter/pull/146880 due to an outdated test result ## Original description - Update CS and googlesource.com link branches - Update GitHub /blob/ and /tree/ links Tested links manually and fixes a few broken or deprecated links Added a test that validates that `master` isn't used, except for specified repos. Part of https://github.com/flutter/flutter/issues/121564
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# Flutter Attach
|
|
|
|
## Overview
|
|
|
|
A Flutter-command that attaches to applications that have been launched
|
|
without `flutter run` and provides a HotRunner (enabling hot reload/restart).
|
|
|
|
## Usage
|
|
|
|
There are three ways for the attach command to discover a running app:
|
|
|
|
1. If the platform is Fuchsia the module name must be provided, e.g. `$
|
|
flutter attach --module=mod_name`. This can be called either before or after
|
|
the application is started, attach will poll the device if it cannot
|
|
immediately discover the port
|
|
1. On Android and iOS, just running `flutter attach` suffices. Flutter tools
|
|
will search for an already running Flutter app or module if available.
|
|
Otherwise, the tool will wait for the next Flutter app or module to launch
|
|
before attaching.
|
|
1. If the app or module is already running and the specific VM Service port is
|
|
known, it can be explicitly provided to attach via the command-line, e.g.
|
|
`$ flutter attach --debug-port 12345`
|
|
|
|
## Source
|
|
|
|
See the [source](https://github.com/flutter/flutter/blob/main/packages/flutter_tools/lib/src/commands/attach.dart) for the attach command.
|