Error when generate signed apk

Clash Royale CLAN TAG#URR8PPPError when generate signed apk
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 seted the build variant from my module to release and generate an apk again, but this, generated this error:
android:debuggable="false"
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
}
}
...
stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me
– Halim Bezek
Jul 6 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 buildreport folder contents. Please check.
– PravyNandas
Jul 21 at 12:35
11 Answers
11
I had this problem and worked around it by adding
lintOptions {
checkReleaseBuilds false
}
to my build.grade file within the android{ } section.
build.grade
android{ }
This doesn't have any other side effects on the application right?
– committedandroider
Dec 15 '14 at 5:38
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.
– error1337
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
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 at 14:11
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.
[app module]/build/reports/lint-results-yourBuildName-fatal.html
It would be nice if Gradle could make it a little more clear where the error report is generated.
Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54
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 developer.android.com/studio/write/lint– Anigif
May 24 at 8:49
gradlew lint
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 at 9:07
Thanks there was error in my layout file
– Mateen Chaudhry
May 28 at 11:16
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 at 20:17
fix the issues identified by lint
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
}
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
Make sure you defined all the translations in all the string.xml files
string.xml
that was my problem .... add missing translations fix the problem thanks
– Hatem Badawi
Jun 30 at 14:44
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!
***Try this***
buildTypes {
release {
lintOptions {
disable 'MissingTranslation'
checkReleaseBuilds false
abortOnError false
}
minifyEnabled false
signingConfig signingConfigs.release
}
}
worked for me ;) thanks
– vijaycaimi
Apr 26 at 9:49
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
}
Not a good idea. The Lint check is there for a reason.
– justColbs
Jul 17 at 16:10
@justColbs might be you face another issue. Post your issue with log cat may be some one guide you properly.
– Rehan Sarwar
Jul 21 at 7:54
Windows -> references ->Android->lint error checking.
un tick Run full error.......

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
Remove that statement from your manifest altogether, Eclipse will handle that for you on the fly.
You should add the code in project level gradle file for generating apk overwriting over errors
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>
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
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 at 14:10