Is Android documentation wrong about adding android block to top-level build.gradle

Question

...adding the following configuration in your project's top-level build.gradle file:

android {
    ...
    testOptions {
        unitTests.returnDefaultValues = true
    }
}

But doing so results in an error:

Could not find method android() for arguments [...] on root project '...' of type org.gradle.api.Project.

Open File

When researching that error:

I find several existing StackOverflows that indicate it is wrong to add adroid{} to your top-level build.gradle file.

In your top-level file, you can't define an android block.

In your top-level file you can't define an android block

Does that mean the Android documentation is wrong?

If not, please help me to understand.

OK so which file did you *actually* add the `android` block into? — Stephen C, Jul 06 '18 at 23:24

score 1 · Accepted Answer · answered Jul 06 '18 at 22:38

Good finding. Yes it's wrong, since there is no android method in lot level gradle file.

I guess they meant project wide gradle file, that should be app/build.gradle.

Also here in documentation you can see that top-level gradle file just configures all modules.

1 Answers1