app lintVitalRelease error when generating signed apk

Question

I ve tried to upload my apk on google play and encountered an error message   quot 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  quot  Then I wrote android debuggable  quot false quot  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

User · Answer

Windows -  references - Android- lint error checking   un tick Run full error

User · Answer

Hello Guys this worked for me  I just modify 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

User · Answer

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

User · Answer

Just find the error reason in here and fix it   yourProject app build reports lint-results-release-fatal xml

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

I had this problem and solved it by adding   lintOptions         checkReleaseBuilds false      to my build gradle file within the android    section

User · Answer

You can find more info choosing assemble from gradle build tab

User · Answer

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    lt string translatable  false  name  stringname  gt This string doesn t need translation lt  string gt

User · Answer

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

User · Answer

Try this      buildTypes           release               lintOptions                   disable  MissingTranslation                  checkReleaseBuilds false                 abortOnError false                           minifyEnabled false             signingConfig signingConfigs release

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

If you add in app gradle under android   lintOptions        quiet true     abortOnError false        It will get work

User · Answer

Try below code  buildTypes       release           lintOptions               disable  MissingTranslation              checkReleaseBuilds false             abortOnError false                   minifyEnabled false         signingConfig signingConfigs release

User · Answer

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

User · Answer

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

User · Answer

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   This string doesn t need translation

User · Answer

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

User · Answer

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

User · Answer

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

[java] ':app:lintVitalRelease' error when generating signed apk

Examples related to java

Examples related to android

Examples related to gradle