':app:lintVitalRelease' error when generating signed apk

Question

I've tried to upload my apk on google play and encountered an error message: "You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play. Learn more about debuggable APKs."

Then I wrote android:debuggable="false" in my manifest and tried again. I've encountered the same error, so I've set the build variant from my module to release and tried generated an apk again, but this time, this error is generated:

Error:Gradle: Execution failed for task ':app:lintVitalRelease'.
Lint found fatal errors while assembling a release target.
  To proceed, either fix the issues identified by lint, or modify your build script as follows:
  ...
  android {
      lintOptions {
          checkReleaseBuilds false
          // Or, if you prefer, you can continue to check for errors in release builds,
          // but continue the build even when errors are found:
          abortOnError false
      }
  }
  ...

All answers seem to be either not to check for errors or not to abort on errors, but what about finding the problem and correcting it??? Android Studio shows no information about what is wrong... Any one was able to fix this with out ignoring errors? — Federico Alvarez, Apr 19 '18 at 14:10
https://stackoverflow.com/questions/43203415/error-while-generating-signed-apk-when-i-use-google-map go on this page fr answer. its work for me — Halim Bezek, Jul 06 '18 at 20:05
"but what about finding the problem and correcting it???" I thought same but I always overlooked 'Inspection Results' tab on the bottom bar and also build\report folder contents. Please check. — PravyNandas, Jul 21 '18 at 12:35
build/report folder is a very good tip. For me the problem was missing translations, and it was clear from the html report. — Pete, Aug 28 '18 at 22:36
on the error google give you the solution, why didn't you try this???? at first try to understand the error as well as error message — Mafujul, Sep 27 '18 at 18:58
I did answer this question in the following link, and it is working perfect https://stackoverflow.com/questions/24098494/error-when-generate-signed-apk/52140460#52140460 — Yosidroid, May 07 '19 at 12:46
downgrading my android gradle work for me. ( " com.android.tools.build:gradle:3.3.2 " ) — AKASH WANGALWAR, Jul 15 '19 at 11:04

score 447 · Accepted Answer · edited Jul 10 '18 at 21:06

447

I wouldn't recommend turning off the lint checks, they're there for a reason. Instead, check what the error is and fix it.

The error report is saved to [app module]/build/reports/lint-results-yourBuildName-fatal.html. You can open this file in a browser to read about the errors.

It would be nice if Gradle could make it a little more clear where the error report is generated.

edited Jul 10 '18 at 21:06

krishh

1,551
15
28

answered May 08 '18 at 17:25

Graydyn Young

5,041
1
17
19

9

Agree, it's much better to correct the error! It is also possible to generate the report manually with `gradlew lint` or via an IDE, see https://developer.android.com/studio/write/lint – Anigif May 24 '18 at 08:49
3

yes, rright direction. Moreover errors report in that html was well described and the errors were addressed ok, so I just corrected them with ease! – CodeToLife May 26 '18 at 09:07
7

yes it's very annoying when it says `fix the issues identified by lint` but doesn't actually shows those errors or path to report... – user25 May 28 '18 at 20:17
8

This must be the accepted answer. Disabling lint is not a good solution. – slhddn Jul 05 '18 at 12:32
1

in my case the error was `MissingTranslation: Incomplete translation` - question for Google: **why isn't this shown in Android Studio??** It's called a `integrated development environment` for a reason. – Someone Somewhere Aug 26 '18 at 12:54
This works! I had an error in a layout where an id doesn't exist. Thanks – Crono Oct 29 '18 at 23:00
in my case autogenerated dimens for large and xlarge config were missing some of the values, would never find out if you did not point me where to look. Big thank you sir. – Boris Gafurov Mar 26 '19 at 14:08
Thank you , when I check the report I found multiple ID in one layout caused this problem – Mouaad Abdelghafour AITALI Aug 09 '19 at 18:41
This should be the accepted answer, I was lucky to browse the page down! Somebody should mark the answer as the good one – Ramon Dec 03 '19 at 11:03
running `gradlew lint --debug` in Android studio Terminal will show you the path where the error report is saved – Bosco Jan 29 '20 at 14:26
Thank you very much for tip. In my case I had fragment registered in Manifest as activity. Build was working fine unless I tried to sign APP. In report I was able to find exact problem. – Michal Zhradnk Nono3551 Jun 10 '20 at 09:56
1

There is not report folder! – roghayeh hosseini Aug 26 '21 at 08:48
No report folder, and the report folder I could find with the files are empty. – Wesley Barnes Nov 12 '21 at 19:36
Your answer works perfectly – Noman Shakoor Feb 16 '22 at 12:05

score 223 · Answer 2 · edited Jun 20 '20 at 00:42

223

I had this problem and solved it by adding:

lintOptions { 

    checkReleaseBuilds false

}

to my build.gradle file within the android{ } section.

edited Jun 20 '20 at 00:42

Samir Alakbarov

1,120
11
21

answered Jun 20 '14 at 21:39

naile

2,319
1
10
2

This doesn't have any other side effects on the application right? – committedandroider Dec 15 '14 at 05:38
13

No, turning lint off will not cause any side effects on the application. Lint is a code-analysis tool and the error mentioned here caused by setting the debuggable property can be viewed in detail in the "lint-results-release-fatal.html" file in the build/outputs folder. – novas1r1 Jul 15 '15 at 13:08
Had trouble adding an android {} section to my top-level build.grade file; so followed some other advice and added this to my build.grade file at the level of the app, i.e. one folder further down, where the android section was already present. – Martin Zaske Sep 22 '17 at 15:27
15

*Warning:* This simply disables the lint checks. It'd be better to at least take a look on the errors before disabling them. In my case, they were about some missing strings for specific languages. Hit "Analyze" -> "Inspect code .." – Markus May 29 '18 at 14:11
2

I don't recommend this. In my case ignoring these warnings would cause crashes at run-time caused by missing resources. Please review lint-results-release-fatal.html and fix all the issues. – Paweł Nadolski Jan 24 '19 at 13:29
The path to `lint-results-release-fatal.html` is `app -> build -> reports` – Lal Feb 25 '19 at 20:40
i dont have an android section in build.gradle – jim May 11 '19 at 05:55
I do not recommend this because it excludes all other errors also while creating release build so please do not use this. It's better to solve error from build->reports->lint-results-release-fatal.html and solve error. – khushbu Jan 03 '20 at 10:17
1

it gave white screen in my case. -1 – Nijat Mursali Apr 21 '21 at 17:21

Yosidroid · Answer 3 · 2021-08-29T18:12:40.437

83

if you want to find out the exact error go to the following path in your project: /app/build/reports/lint-results-release-fatal.html(or .xml). The easiest way is if you go to the xml file, it will show you exactly what the error is including its position of the error in your either java class or xml file. Turning off the lint checks is not a good idea, they're there for a reason. Instead, go to:

    /app/build/reports/lint-results-release-fatal.html or 
    /app/build/reports/lint-results-release-fatal.xml

and fix it.

In Kotlin is different. First you need to set the following code in Android section of build.gradel of the app folder.

     android {
          :
          lintOptions {
            baseline(file("lint-baseline.xml"))
          }
      }

Then run lint from the IDE (Analyze > Inspect Code) or from the command line as follows.

      $ ./gradlew lintDebug

...

The output prints the location of the lint-baseline.xml file within app folder but sometimes within app/src folder as well /app/lint-baseline.xml

edited Aug 29 '21 at 18:12

answered Sep 02 '18 at 19:40

Yosidroid

2,053
16
15

2

This is way better than just ignore the errors and move on. And the HTML file is so easy to understand the problem. – John Pang Nov 28 '18 at 03:07
i found the problem in /app/build/reports/lint-results-release-fatal.xml. thanks – Bukunmi May 29 '19 at 14:48
There is not report folder! – roghayeh hosseini Aug 26 '21 at 08:47
@roghayeh hossein if you are using kotlin, You won't find report folder. There is another way of finding your lint files. I just updated my answers, you can check it back. – Yosidroid Aug 29 '21 at 18:16

score 51 · Answer 4 · answered Apr 26 '18 at 08:57

51

Make sure you defined all the translations in all the string.xml files

answered Apr 26 '18 at 08:57

Roberto

4,524
1
38
30

score 43 · Answer 5 · answered May 14 '18 at 10:06

43

In case that you may trying to locate where the problem is, I found mine in the following path of my project: /app/build/reports/lint-results-release-fatal.html(or .xml).

Hope this helps!

answered May 14 '18 at 10:06

Pecolyte Wang

431
4
2

7

both are files are empty for me. – m9m9m Jan 21 '19 at 05:05

score 38 · Answer 6 · edited Sep 15 '17 at 08:29

38

I have faced same issue when creating signed apk from android studio. I just change little bit change on build.gradle file inside android {}

lintOptions {
        checkReleaseBuilds false
        abortOnError false
    }

edited Sep 15 '17 at 08:29

Aveek

849
1
12
28

answered May 25 '15 at 10:20

Dhruv Raval

4,946
3
29
34

This worked for me. I had a similar issue. Execution failed for task ‘:app:lint***Release’. > org.picocontainer.MutablePicoContainer.registerComponentInstance(Ljava/lang/Object;)Lorg/picocontainer/ComponentAdapter; – Nelson Ramirez Nov 17 '17 at 19:29

score 32 · Answer 7 · answered Jan 27 '19 at 07:38

32

How to find error details

Anylyze -> Inspect Code

Then in Inspection Results you will see an error

In my case build failed due to unresolved javadoc reference in Google IAP

answered Jan 27 '19 at 07:38

Mikhail

2,612
3
22
37

4

This should be the accepted answer. To all the people who suggested to disable the lint checking, that is just a work around. It is still better to fix the error than skip it. Skipping lint checks should only be done in very specific cases and not all the time. AGAIN, THAT SHOULD BE DONE RARELY OR EVEN NOT AT ALL. – Archie G. Quiñones Mar 15 '19 at 05:39

score 22 · Answer 8 · answered Aug 04 '17 at 07:47

***Try this***

 buildTypes {
        release {
            lintOptions {
                disable 'MissingTranslation'
                checkReleaseBuilds false
                abortOnError false
            }
            minifyEnabled false
            signingConfig signingConfigs.release
        }
    }

Mateusz Kaflowski · Answer 9 · 2022-07-26T13:36:48.233

18

You can find more info choosing assemble from gradle build tab:

EDIT 2022:

You can run after clicking elephant button:

gradle assembleDebug

edited Jul 26 '22 at 13:36

answered Oct 03 '18 at 09:51

Mateusz Kaflowski

2,221
1
29
35

5

this is the actual answer, go to the assemble in app, in gradle window and run it by double clicking, Android studio will tell you exactly what it was poping. – Wajid Nov 21 '18 at 18:52
1

Oh my god... thanks! That one saved me a lot of time! :D – thinklinux Apr 19 '19 at 12:52
I got, `lintOptions { checkReleaseBuilds false // Or, if you prefer, you can continue to check for errors in release builds, // but continue the build even when errors are found: abortOnError false }` and i added it but i got the same error in every time i build a release – Oliver D Nov 29 '19 at 17:02

score 12 · Answer 10 · answered Nov 29 '17 at 10:15

12

Try These 3 lines in your app.gradle file.

android {
lintOptions {
    checkReleaseBuilds false
    // Or, if you prefer, you can continue to check for errors in release builds,
    // but continue the build even when errors are found:
    abortOnError false
}

answered Nov 29 '17 at 10:15

Rehan Sarwar

994
8
20

@justColbs might be you face another issue. Post your issue with log cat may be some one guide you properly. – Rehan Sarwar Jul 21 '18 at 07:54

score 9 · Answer 11 · edited Jun 06 '22 at 07:46

This worked for me, I just modified my BuildTypes like this:

buildTypes {
    release {
        android {
            lintOptions {
                checkReleaseBuilds false
                // Or, if you prefer, you can continue to check for errors in release builds,
                // but continue the build even when errors are found:
                abortOnError false
            }
        }
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

score 9 · Answer 12 · answered Feb 19 '20 at 04:05

Add this inside android {} build.gradle(Module:App)

lintOptions {
    checkReleaseBuilds false
    // Or, if you prefer, you can continue to check for errors in release builds,
    // but continue the build even when errors are found:
    abortOnError false
}

score 8 · Answer 13 · edited Jun 06 '22 at 07:47

8

My problem was a missing translation. I had a settings.xml that was not translated as it was not needed, so I had to add "translatable="false" to the strings:

<string translatable="false" name="stringname">This string doesn't need translation</string>

edited Jun 06 '22 at 07:47

Stephen Ostermiller

23,933
14
88
109

answered Sep 19 '18 at 10:24

Harsh Masand

121
1
4

score 8 · Answer 14 · answered Oct 04 '19 at 16:40

8

Just find the error reason in here and fix it.

yourProject/app/build/reports/lint-results-release-fatal.xml

answered Oct 04 '19 at 16:40

Amir Hossein Ghasemi

20,623
10
57
53

1

you should know what exact error and recertify. thank you. – Asesha George Dec 10 '19 at 12:42
I found `TargetSdkVersion No Longer Supported: Google Play requires that apps target API level 26 or higher.` in my log, i.e. can't set `targetSdkVersion` 25. – 林果皞 Jan 13 '20 at 10:38

tomDev · Answer 15 · 2018-07-26T19:01:50.903

7

My problem was a missing translation. I had a settings.xml that was not translated as it was not needed, so I had to add "translatable="false" to the strings:

<string translatable="false" name="stringname">This string doesn't need translation</string>

edited Jul 26 '18 at 19:01

answered Jul 26 '18 at 18:40

tomDev

5,620
5
29
39

Keshav Gera · Answer 16 · 2020-01-28T09:36:19.530

Solve this Issue Using this in build.gradle (app) File Inside main Android { inside }

  buildTypes {
      //  crunchPngs false // or true   when png error
        release {
            lintOptions {
                checkReleaseBuilds false
                abortOnError false
            }
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

score 4 · Answer 17 · answered Dec 21 '19 at 21:21

As many people have suggested, it is always better to try and fix the error from the source. check the lint generated file

/app/build/reports/lint-results-release-fatal.html

read the file and you will be guided to where the error is coming from. Check out mine: the error came from improper view constraint.

score 3 · Answer 18 · edited Oct 20 '18 at 16:53

3

Try below code

buildTypes {
    release {
        lintOptions {
            disable 'MissingTranslation'
            checkReleaseBuilds false
            abortOnError false
        }
        minifyEnabled false
        signingConfig signingConfigs.release
    }
}

edited Oct 20 '18 at 16:53

Sandy.....

2,833
2
15
26

answered Oct 20 '18 at 15:21

Sheikh Ahmed Qureshi

31
2

score 2 · Answer 19 · answered Feb 06 '15 at 05:11

2

Windows -> references ->Android->lint error checking.

un tick Run full error.......

enter image description here

answered Feb 06 '15 at 05:11

someone

6,577
7
37
60

1

Very pretty, but where is this window from please? I could not find it in Android Studio... – Martin Zaske Sep 22 '17 at 15:29

score 2 · Answer 20 · edited Nov 11 '18 at 19:21

2

Go to build.gradle(Module:app)

lintOptions {
    checkReleaseBuilds false
    // Or, if you prefer, you can continue to check for errors in release builds,
    // but continue the build even when errors are found:
    abortOnError false
}

edited Nov 11 '18 at 19:21

Christian Gollhardt

16,510
17
74
111

answered Nov 11 '18 at 19:02

Azmat Ali

554
5
7

score 1 · Answer 21 · answered Jun 07 '14 at 15:06

1

Remove that statement from your manifest altogether, Eclipse will handle that for you on the fly.

answered Jun 07 '14 at 15:06

Eran Goldin

980
12
21

score 1 · Answer 22 · answered Mar 13 '19 at 21:10

1

In my case the problem was related to minimum target API level that is required by Google Play. It was set less than 26.

Issue disappeared when I set minimum target API level to 26.

answered Mar 13 '19 at 21:10

mdicosimo

724
7
19

score 1 · Answer 23 · answered May 07 '19 at 12:56

1

    lintOptions {
      checkReleaseBuilds false
      abortOnError false
    }

The above code can fix the problem by ignoring it, but it may result in crashing the app as well.

The good answer is in the following link:

Error when generate signed apk

answered May 07 '19 at 12:56

Yosidroid

2,053
16
15

score 1 · Answer 24 · answered Apr 16 '21 at 07:50

1

Don't disable the lint option

Check the Lint Report for error and warning

PATH:

YourAppProjectFolder\app\build\reports

Solve all error and warning:)

answered Apr 16 '21 at 07:50

Swarnava Chakraborty

147
1
4

score 0 · Answer 25 · answered Feb 18 '17 at 08:25

0

You should add the code in project level gradle file for generating apk overwriting over errors

answered Feb 18 '17 at 08:25

Kamal

245
2
3

score 0 · Answer 26 · answered Aug 03 '20 at 03:30

0

This problem came to me when I updated the Android Gradle Plugin Version to 4.0.1 and the Gradle version to 6.1.1.

If someone is in a hurry, just downgrade the Gradle Plugin Version to 3.6.3 and the Gradle version to 5.6.4. It worked for me.

answered Aug 03 '20 at 03:30

Jeiel Junio

129
1
10

score 0 · Answer 27 · answered Dec 12 '21 at 12:07

Upgrading gradle distribution url to,

// android/gradle/wrapper/gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0.2-all.zip

and upgrading buildscript -> dependencies -> classpath to,

// android/build.gradle
classpath 'com.android.tools.build:gradle:7.0.0'

fixed the issue for me

score -1 · Answer 28 · answered Nov 22 '18 at 17:38

-1

If you add in app.gradle under android{

lintOptions {

    quiet true
    abortOnError false
}

}

It will get work

answered Nov 22 '18 at 17:38

Alpesh Sorathiya

510
3
13

I think it is better to fix lints and errors, if possible, instead of skip the check – Piero Feb 03 '19 at 11:08
It works for me in CI/CD build. – Frank Feng Apr 08 '22 at 20:39

':app:lintVitalRelease' error when generating signed apk

28 Answers28

Linked

Related