Sunteți pe pagina 1din 1

Search… Log In Sign Up

Home

PUBLIC

Stack Overflow

Tags
Error when generate signed apk Ask Question
Users

Jobs I've tried to upload my apk on google play and encountered an error message: "You uploaded a asked 4 years, 8 months ago
debuggable APK. For security reasons you need to disable debugging before it can be published in
viewed 92,580 times
143 Google Play. Learn more about debuggable APKs."
Teams active 7 days ago
Q&A for work 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,
Learn More generated this error:
BLOG
21
Error:Gradle: Execution failed for task ':app:lintVitalRelease'.
Lint found fatal errors while assembling a release target. Stack Overflow & InfoJobs: Bringing
To proceed, either fix the issues identified by lint, or modify your build script as follows Opportunities to Developers in Spain
...
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
}
}
...

java android gradle

share improve this question edited Feb 6 '15 at 5:06 asked Jun 7 '14 at 14:58
Pang user3716366
6,901 16 64 102 719 2 5 4
Linked
18 All answers seem to be either not to check for errors or not to abort on errors, but what about finding the
0 Error message in Android Studio
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
10 Error: Execution failed for task ':app:
stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me – Halim Bezek Jul 6 '18 at lintVitalRelease' any one can solve it?
20:05
1 Error while generating signed apk when i
3 "but what about finding the problem and correcting it???" I thought same but I always overlooked 'Inspection use google map?
Results' tab on the bottom bar and also build\report folder contents. Please check. – PravyNandas Jul 21 '18 at
12:35 -1 How to Create an APK in Android Studio?

1 build/report folder is a very good tip. For me the problem was missing translations, and it was clear from the 0 Error display where generate singed APK
html report. – Pete Aug 28 '18 at 22:36 from android studio

on the error google give you the solution, why didn't you try this???? at first try to understand the error as well 1 Error generating signed apk with nothing in
as error message – Mafujul Sep 27 '18 at 18:58 lint-results-release-fatal

add a comment
Related
20 Answers active oldest votes 2735 When to use LinkedList over ArrayList in
Java?

3100 How do I generate random integers within a


I wouldn't recommend turning off the lint checks, they're there for a reason. Instead, check what the specific range in Java?
error is and fix it.
1805 “Debug certificate expired” error in Eclipse
242 The error report is saved to [app module]/build/reports/lint-results-yourBuildName-fatal.html .
Android plugins

You can open this file in a browser to read about the errors. 1106 Is there a way to get the source code from
an APK file?
It would be nice if Gradle could make it a little more clear where the error report is generated.
83 Android Studio: how to generate signed
share improve this answer edited Jul 10 '18 at 21:06 answered May 8 '18 at 17:25 apk using Gradle?

Krish Graydyn Young 0 Google Play not accepting APK


767 9 23 2,798 1 10 14
5 Gradle is generating debuggable APKs on
release mode
8 Thanks! You saved my day. A perfect answer indeed. – Thunder Dragon May 14 '18 at 16:54

5 Agree, it's much better to correct the error! It is also possible to generate the report manually with gradlew 61 Android Signed APK showing as Unsigned
lint or via an IDE, see developer.android.com/studio/write/lint – Anigif May 24 '18 at 8:49 APK when trying to upload to production

3 yes, rright direction. Moreover errors report in that html was well described and the errors were addressed ok, so 0 Add RSA key to Android project in a secure
I just corrected them with ease! – CodeToLife May 26 '18 at 9:07 way

3 yes it's very annoying when it says fix the issues identified by lint but doesn't actually shows those 0 java.lang.NullPointerException (no error
errors or path to report... – user25 May 28 '18 at 20:17 message) when try to make sign apk

3 This must be the accepted answer. Disabling lint is not a good solution. – slhddn Jul 5 '18 at 12:32
Hot Network Questions
show 5 more comments
Do hard to pronounce names break immersion?

Find the needle in the haystack

Finding answers within your organization can be as easy as finding this one... Learn more We're waiting in a BIG or LONG queue?

Male or female header on PCB?

How can I adjudicate a character attempting a


"shield crush" attack to pin a creature?

Why is ostracism called 村八分【むらはちぶ】?


I had this problem and worked around it by adding
Can You Explain How Tarjan's Pseudocode Works
lintOptions { to Someone Familiar with C or Java?
144
Breaking in to the employee's office computer
checkReleaseBuilds false
What's the point in placing small barcode stickers
} on one's check-in bags?

Is a connected set always an uncountably infinite


to my build.grade file within the android{ } section. set?

share improve this answer About to write my PhD thesis and I don't know the
edited Jun 20 '14 at 21:52 answered Jun 20 '14 at 21:39
basics and fundamentals. I am feeling unworthy of
Jamal naile the PhD title. What should I do?
608 6 22 29 1,489 1 5 2
Detecting the outer edge

This doesn't have any other side effects on the application right? – committedandroider Dec 15 '14 at 5:38 Why are these LED current limiting resistors so
big?
6 No, turning lint off will not cause any side effects on the application. Lint is a code-analysis tool and the error Does it make sense to consider a triggerable
mentioned here caused by setting the debuggable property can be viewed in detail in the "lint-results-release- server software crash a DOS attack?
fatal.html" file in the build/outputs folder. – error1337 Jul 15 '15 at 13:08
I get bored when people talk too much in
Had trouble adding an android {} section to my top-level build.grade file; so followed some other advice and meetings. What should I do?
added this to my build.grade file at the level of the app, i.e. one folder further down, where the android section
Why does schwa have a special place among
was already present. – Martin Zaske Sep 22 '17 at 15:27
vowels?
9 Warning: This simply disables the lint checks. It'd be better to at least take a look on the errors before disabling Why do we spell the word “who” with a silent “w”
them. In my case, they were about some missing strings for specific languages. Hit "Analyze" -> "Inspect code when it isn’t needed?
.." – Markus May 29 '18 at 14:11
Writing over fractions
I don't recommend this. In my case ignoring these warnings would cause crashes at run-time caused by missing
Decrease in temperature of a aqueous salt
resources. Please review lint-results-release-fatal.html and fix all the issues. – Paweł Nadolski Jan 24 at 13:29
solution decreases conductivity
add a comment What is the purpose of auto-login? Is it
safe/secure?

Name the Third Friend


Make sure you defined all the translations in all the string.xml files
How can I launch a projectile into orbit using only
geological structures and power sources?
share improve this answer answered Apr 26 '18 at 8:57
44 are all cubic graphs almost Hamiltonian?
Roberto
2,189 21 20 Why did Harry Potter trust Snape?

that was my problem .... add missing translations fix the problem thanks – Hatem Badawi Jun 30 '18 at 14:44 question feed

Worked for me some translations were missing. – Himanshu Rawat Aug 2 '18 at 2:54

this worked for me – Shabeer Ali Aug 24 '18 at 3:58

add a comment

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
33 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.

share improve this answer answered Sep 2 '18 at 19:40


Josi
363 3 6

VERY USEFUL! thanks! work for me – HerberthObregon Oct 1 '18 at 6:01

2 This should be marked as Accepted answer. – scienticious Nov 13 '18 at 10:40

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 3:07

Upvote to infinity. – IlToro Nov 28 '18 at 18:10

Thanks, worked for me. perfect solution – Narh-ngwah Ebenezer Watts Jan 6 at 11:55

add a comment

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

share improve this answer edited Sep 15 '17 at 8:29 answered May 25 '15 at 10:20
Aveek Dhruv Raval
429 1 5 19 3,779 23 29

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/Com
ponentAdapter; – Nelson Ramirez Nov 17 '17 at 19:29

add a comment

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).
29 Hope this helps!

share improve this answer answered May 14 '18 at 10:06


Pecolyte Wang
291 2 2

This should be accepted answer. Easily found what was wrong and fixed. – Vadim Sep 19 '18 at 7:24

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

add a comment

***Try this***

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

share improve this answer answered Aug 4 '17 at 7:47


Amit raj
266 3 7

worked for me ;) thanks – vijaycaimi Apr 26 '18 at 9:49

add a comment

Try These 3 lines in your app.gradle file.

android {
8 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
}

share improve this answer answered Nov 29 '17 at 10:15


Rehan Sarwar
356 2 13

Not a good idea. The Lint check is there for a reason. – justColbs Jul 17 '18 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 '18 at 7:54

add a comment

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:
6 <string translatable="false" name="stringname">This string doesn't need translation</string>

share improve this answer edited Jul 26 '18 at 19:01 answered Jul 26 '18 at 18:40
tomDev
2,955 4 18 28

add a comment

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

share improve this answer answered Oct 3 '18 at 9:51


Mateusz Kaflowski
545 7 23

2 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 Ali Nov 21 '18 at 18:52

add a comment

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

share improve this answer answered Sep 19 '18 at 10:24


Harsh Masand
56 1 4

add a comment

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

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


2

share improve this answer answered Feb 6 '15 at 5:11


Suranga
4,905 6 28 50

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

add a comment

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

share improve this answer answered Jun 7 '14 at 15:06


1
Eran Goldin
745 9 16

add a comment

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

buildTypes {
1 release {
lintOptions {
checkReleaseBuilds false
abortOnError false
}
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}

share improve this answer answered Oct 30 '18 at 6:14


Keshav Gera
2,651 17 28

add a comment

How to find error details

Anylyze -> Inspect Code


1

Then in Inspection Results you will see an error

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

share improve this answer answered Jan 27 at 7:38


Mikhail
877 1 10 25

add a comment

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

share improve this answer answered Feb 18 '17 at 8:25


0
Kamal
73 1 2

add a comment

Try below code

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

share improve this answer edited Oct 20 '18 at 16:53 answered Oct 20 '18 at 15:21
Sandy Sheikh Ahmed Qureshi
1,579 2 7 21 1

add a comment

Hello Guys this worked for me, I just modify my BuildTypes like this:

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

share improve this answer answered Nov 3 '18 at 1:18


DoctorDroid Haiti
54 1 8

add a comment

If you add in app.gradle under android{

lintOptions {
0
quiet true
abortOnError false
}

It will get work

share improve this answer answered Nov 22 '18 at 17:38


Alpesh Sorathiya
228 1 10

I think it is better to fix lints and errors, if possible, instead of skip the check – Piero 20 hours ago

add a comment

Go to build.gradle(Module:app)

lintOptions {
-1 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
}

share improve this answer edited Nov 11 '18 at 19:21 answered Nov 11 '18 at 19:02
Christian Gollhardt Kaiffi
9,796 12 44 75 1 1

add a comment

Your Answer

Sign up or log in Post as a guest


Name
Sign up using Google

Sign up using Facebook Email


Required, but never shown

Sign up using Email and Password

Post Your Answer

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.

Not the answer you're looking for? Browse other questions tagged java android gradle or ask
your own question.

STACK OVERFLOW PRODUCTS COMPANY STACK EXCHANGE Blog Facebook Twitter LinkedIn
NETWORK
Questions Teams About
Technology
Jobs Talent Press
Life / Arts
Developer Jobs Directory Engagement Work Here
Culture / Recreation
Salary Calculator Enterprise Legal
Science
Help Privacy Policy
Other
Mobile Contact Us site design / logo © 2019 Stack Exchange Inc; user contributions
licensed under cc by-sa 3.0 with attribution required.
Disable Responsiveness rev 2019.2.1.32789

S-ar putea să vă placă și