Skip to content

flutter build apk --config-only prints Config complete right before the command exits, which doesn't match other commands #160801

@jmagman

Description

@jmagman
$ flutter build apk --config-only
Downloading android-arm-profile/darwin-x64 tools...                287ms
Downloading android-arm-release/darwin-x64 tools...                134ms
Downloading android-arm64-profile/darwin-x64 tools...              142ms
Downloading android-arm64-release/darwin-x64 tools...              132ms
Downloading android-x64-profile/darwin-x64 tools...                125ms
Downloading android-x64-release/darwin-x64 tools...                123ms

Config complete.

The "Config complete." part is a but odd, since the tool doesn't announce other commands are "complete", including flutter build ios --config-only or flutter build macos --config-only

This is a really tiny nit, and this command isn't used by most flutter devs.

Suggest removing this log line:

_logger.printStatus('Config complete.');

Will have to detect another way that the config-only logic stopped there:
expect(result.stdout, contains(RegExp(r'Config complete')));

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projectteam-androidOwned by Android platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-androidTriaged by Android platform team

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions