The build scan was not published due to a configuration problem

Help/Discuss
1

hi,

i got this error since today.

The build scan was not published due to a configuration problem.
    
   The Gradle Cloud Services license agreement has not been agreed to.
    
   To agree to the license, include the following in your root project's configuration:
    buildScan { licenseAgreementUrl = 'https://gradle.com/terms-of-service'; licenseAgree = 'yes' }
    
   For more information, please see https://gradle.com/scans/help/plugin-license.
    
   Alternatively, if you are using Gradle Enterprise, specify the server location.
    For more information, please see https://gradle.com/scans/help/plugin-enterprise-config.
    
   9:27:52 PM: Task execution finished 'signingReport'.

What appends ? i cannot install the akp anymore ?

thanks for explaination.

2

As the error says.
You try to publish a build scan but did not agree to the license terms.
Either agree to the license terms or do not try to publish a build scan.

3

hi,

i did not try to run any gradlew scan. May be android studio did. I just test it 2 weeks ago to see what is was. But not since ?

Still got the message but AKP are installed. The installation error came from android studio, one more time :grinning:

4

Your output says you did.
Maybe you added some init script that enables it for all builds you are running - which might be a bad idea but is suggested by some questionable tutorials for example.

5

no it append i think because i used android studio 2022 and gradle 4.6 for the Project(testing). But i got the message on android studio 4.1 and gradle 4.4. now.

6

It would be new to me that AS tries to automatically enable build scans for you.
That would be pretty fatal, as that means that data about the builds is sent to a Gradle server.
I cannot imagine that anything is doing this automatically for you.

7

sure i did it once on AS 4.1 and gradle 4.4. I just run once or two it from the terminal.

I agree with the bad idéa to always run scan. But if it is running it must be somewhere in gradle file ? or during the run ?

I search for scan in the all project and got nothing in relation with gradle ?

8

It can be in the build scripts, it can be in a plugin you apply, it can be in the arguments you invoke, it can be in an init script, …

9

It can be anywhere :grinning:

So i need to do a search in the project directorie. But what would be the name to search. I already tried “scan” but i could not see nothing interresting.

10

So if i do not want the scan i got nothing to add.
But if i want it what shall i do ? :grinning:

11

I does not have to be in the project.
As I said, it could for example also come from an init script for example.
If you do want the scan, do what the error tells you and accept the terms of service. :slight_smile: