The Remote Control Service offers an API for querying and connecting to arbitrary FIDL services on the target.
Queries can match an arbitrary number of services on the system, and
will output all of the matches, formatted according to their place in the
In the special case of a query that uniquely matches a single service, RCS can connect to that service and pass a handle to it to the host for FFX to use. This is how the the plugin system is able to create FIDL proxies using the component selector mapping.
To query for services on a target, write a selector to match the service(s) of interest.
ffx commands that interact with components or services take component
selectors as a parameter. Component selectors in
ffx use the same syntax as
the diagnostics selectors.
Here are some example selectors, all of which select the Remote Control Service:
core/remote-control:out:fuchsia.developer.remotecontrol.RemoteControl core/*:out:fuchsia.developer.remotecontrol.RemoteControl core/*:expose:fuchsia.developer.remotecontrol.RemoteControl core/remote-control:out:* core/*:expose:fuchsia.developer.remotecontrol.R*
There are three constituent segments of a selector:
<component moniker>:<node selector>:<property selector>. Each is discussed
below. The wildcard (
*) is valid in each segment of a selector.
Consider this example:
outis the node selector. In
ffx, this must be one of the following values, which correspond to the routing terminology used in the component manifest and defined in routing terminology documentation.
out: services offered by the component. Corresponds to
offerin the component manifest.
expose: services exposed by the component. Corresponds to
exposein the component manifest.
in: services depended upon by the component. Corresponds to
usein the component manifest.
fuchsia.developer.remotecontrol.RemoteControlis the property selector and is matched against fully-qualified FIDL service names in the routing directories matched by the node selector.
You may optionally omit the property selector: