Support --flavor argument in the debugger

flutter run accepts --flavor for Android product flavors and Xcode schemes. If you’re using one of the aforementioned, debugging will fail with the following error (Android):

The Gradle project does not define a task suitable for the requested build.
The android/app/build.gradle file defines product flavors: <list of flavor options>
You must specify a --flavor option to select one of them.

For context, this is the flag description:

--flavor                       Build a custom app flavor as defined by platform-specific build setup.
                                   Supports the use of product flavors in Android Gradle scripts.
                                   Supports the use of custom Xcode schemes.

[DanTup]

Ok, I think maybe the existing args already supports this. I just set my launch.json like this:

{
	"name": "Flutter",
	"request": "launch",
	"type": "flutter",
	"args": [
		"--flavor",
		"red"
	]
}

When I hit F5, I get this in the debug console:

The Gradle project does not define a task suitable for the requested build.
The android/app/build.gradle file does not define any custom product flavors.
You cannot use the --flavor option.

So, I don’t think we need to do anything here. We could add an additional flavor setting, but I don’t know how much value there is in it. Any opinions?

[devoncarew]

I don’t have a sample project for this myself; @lukef may?

Here’s how we expose it in IntelliJ:

It’s a free-form text field; if there’s something in there, then we pass --flavor=xxx in via flutter run, else we don’t pass the flag. Since these are defined in gradle (or ios) files, we don’t try and to any validation of the flavor param client side.