Error when generate signed apk

133

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:

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

      }

  }

  ...

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

16

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

stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me
– Halim Bezek
Jul 6 at 20:05

3

"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

1

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 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 at 18:58

add a comment |

133

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

      }

  }

  ...

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

16

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

stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me
– Halim Bezek
Jul 6 at 20:05

3

"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

1

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 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 at 18:58

add a comment |

133

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

      }

  }

  ...

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

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

      }

  }

  ...

java android gradle

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

edited Feb 6 '15 at 5:06

Pang

6,8601563101

edited Feb 6 '15 at 5:06

Pang

6,8601563101

edited Feb 6 '15 at 5:06

Pang

6,8601563101

asked Jun 7 '14 at 14:58

user3716366

669254

asked Jun 7 '14 at 14:58

user3716366

669254

asked Jun 7 '14 at 14:58

user3716366

669254

16

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

stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me
– Halim Bezek
Jul 6 at 20:05

3

"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

1

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 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 at 18:58

add a comment |

16

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

stackoverflow.com/questions/43203415/… go on this page fr answer. its work for me
– Halim Bezek
Jul 6 at 20:05

3

"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

1

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 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 at 18:58

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

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

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 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 at 18:58

add a comment |

19 Answers
19

active

oldest

votes

219

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 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

8

Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54

5

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

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 at 9:07

3

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

3

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

|
show 5 more comments

137

I had this problem and worked around it by adding

lintOptions { 



    checkReleaseBuilds false



}

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

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

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

6

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

8

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

add a comment |

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

answered Apr 26 at 8:57

Roberto

2,1292120

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

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

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

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

Hope this helps!

answered May 14 at 10:06

Pecolyte Wang

29122

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

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

lintOptions {

        checkReleaseBuilds false

        abortOnError false

    }

edited Sep 15 '17 at 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

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

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

answered Sep 2 at 19:40

Josi

29336

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

1

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

add a comment |

***Try this***



 buildTypes {

        release {

            lintOptions {

                disable 'MissingTranslation'

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            signingConfig signingConfigs.release

        }

    }

answered Aug 4 '17 at 7:47

Amitraj

24636

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

add a comment |

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

346213

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

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:

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

edited Jul 26 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

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:

This string doesn't need translation

answered Sep 19 at 10:24

Harsh Masand

5614

add a comment |

You can find more info choosing assemble from gradle build tab: enter image description here

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

1

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 at 18:52

add a comment |

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

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

enter image description here

answered Feb 6 '15 at 5:11

Suranga

4,86062850

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.

answered Jun 7 '14 at 15:06

Eran Goldin

745916

add a comment |

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

  buildTypes {

        release {

            lintOptions {

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

answered Oct 30 at 6:14

Keshav Gera

2,4031727

add a comment |

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

answered Feb 18 '17 at 8:25

Kamal

7312

add a comment |

Try below code

buildTypes {

    release {

        lintOptions {

            disable 'MissingTranslation'

            checkReleaseBuilds false

            abortOnError false

        }

        minifyEnabled false

        signingConfig signingConfigs.release

    }

}

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

add a comment |

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'

        }

    }

answered Nov 3 at 1:18

DoctorDroid Haiti

467

add a comment |

If you add in app.gradle under android{

lintOptions {



    quiet true

    abortOnError false

}

}

It will get work

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

add a comment |

-1

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 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f24098494%2ferror-when-generate-signed-apk%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

19 Answers
19

active

oldest

votes

19 Answers
19

active

oldest

votes

219

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 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

8

Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54

5

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

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 at 9:07

3

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

3

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

|
show 5 more comments

219

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 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

8

Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54

5

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

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 at 9:07

3

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

3

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

|
show 5 more comments

219

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 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

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 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

edited Jul 10 at 21:06

Krish

757923

edited Jul 10 at 21:06

Krish

757923

edited Jul 10 at 21:06

Krish

757923

answered May 8 at 17:25

Graydyn Young

2,5681914

answered May 8 at 17:25

Graydyn Young

2,5681914

answered May 8 at 17:25

Graydyn Young

2,5681914

8

Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54

5

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

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 at 9:07

3

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

3

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

|
show 5 more comments

8

Thanks! You saved my day. A perfect answer indeed.
– Thunder Dragon
May 14 at 16:54

5

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

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 at 9:07

3

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

3

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

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

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

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

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

|
show 5 more comments

137

I had this problem and worked around it by adding

lintOptions { 



    checkReleaseBuilds false



}

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

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

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

6

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

8

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

add a comment |

137

I had this problem and worked around it by adding

lintOptions { 



    checkReleaseBuilds false



}

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

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

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

6

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

8

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

add a comment |

137

I had this problem and worked around it by adding

lintOptions { 



    checkReleaseBuilds false



}

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

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

I had this problem and worked around it by adding

lintOptions { 



    checkReleaseBuilds false



}

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

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

edited Jun 20 '14 at 21:52

Jamal

60662229

edited Jun 20 '14 at 21:52

Jamal

60662229

edited Jun 20 '14 at 21:52

Jamal

60662229

answered Jun 20 '14 at 21:39

naile

1,419152

answered Jun 20 '14 at 21:39

naile

1,419152

answered Jun 20 '14 at 21:39

naile

1,419152

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

6

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

8

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

add a comment |

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

6

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

8

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

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

add a comment |

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

answered Apr 26 at 8:57

Roberto

2,1292120

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

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

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

add a comment |

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

answered Apr 26 at 8:57

Roberto

2,1292120

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

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

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

add a comment |

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

answered Apr 26 at 8:57

Roberto

2,1292120

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

answered Apr 26 at 8:57

Roberto

2,1292120

answered Apr 26 at 8:57

Roberto

2,1292120

answered Apr 26 at 8:57

Roberto

2,1292120

answered Apr 26 at 8:57

Roberto

2,1292120

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

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

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

add a comment |

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

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

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

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

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

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

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

Hope this helps!

answered May 14 at 10:06

Pecolyte Wang

29122

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

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

Hope this helps!

answered May 14 at 10:06

Pecolyte Wang

29122

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

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

Hope this helps!

answered May 14 at 10:06

Pecolyte Wang

29122

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 at 10:06

Pecolyte Wang

29122

answered May 14 at 10:06

Pecolyte Wang

29122

answered May 14 at 10:06

Pecolyte Wang

29122

answered May 14 at 10:06

Pecolyte Wang

29122

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

add a comment |

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

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

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

lintOptions {

        checkReleaseBuilds false

        abortOnError false

    }

edited Sep 15 '17 at 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

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

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

lintOptions {

        checkReleaseBuilds false

        abortOnError false

    }

edited Sep 15 '17 at 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

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

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

lintOptions {

        checkReleaseBuilds false

        abortOnError false

    }

edited Sep 15 '17 at 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

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 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

edited Sep 15 '17 at 8:29

Aveek

4191519

edited Sep 15 '17 at 8:29

Aveek

4191519

edited Sep 15 '17 at 8:29

Aveek

4191519

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

answered May 25 '15 at 10:20

Dhruv Raval

3,7192328

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

add a comment |

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

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

add a comment |

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

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

and fix it.

answered Sep 2 at 19:40

Josi

29336

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

1

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

add a comment |

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

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

and fix it.

answered Sep 2 at 19:40

Josi

29336

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

1

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

add a comment |

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

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

and fix it.

answered Sep 2 at 19:40

Josi

29336

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

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

and fix it.

answered Sep 2 at 19:40

Josi

29336

answered Sep 2 at 19:40

Josi

29336

answered Sep 2 at 19:40

Josi

29336

answered Sep 2 at 19:40

Josi

29336

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

1

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

add a comment |

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

1

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

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

This should be marked as Accepted answer.
– scienticious
Nov 13 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 at 3:07

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

add a comment |

***Try this***



 buildTypes {

        release {

            lintOptions {

                disable 'MissingTranslation'

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            signingConfig signingConfigs.release

        }

    }

answered Aug 4 '17 at 7:47

Amitraj

24636

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

add a comment |

***Try this***



 buildTypes {

        release {

            lintOptions {

                disable 'MissingTranslation'

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            signingConfig signingConfigs.release

        }

    }

answered Aug 4 '17 at 7:47

Amitraj

24636

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

add a comment |

***Try this***



 buildTypes {

        release {

            lintOptions {

                disable 'MissingTranslation'

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            signingConfig signingConfigs.release

        }

    }

answered Aug 4 '17 at 7:47

Amitraj

24636

***Try this***



 buildTypes {

        release {

            lintOptions {

                disable 'MissingTranslation'

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            signingConfig signingConfigs.release

        }

    }

answered Aug 4 '17 at 7:47

Amitraj

24636

answered Aug 4 '17 at 7:47

Amitraj

24636

answered Aug 4 '17 at 7:47

Amitraj

24636

answered Aug 4 '17 at 7:47

Amitraj

24636

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

add a comment |

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

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

add a comment |

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

346213

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

add a comment |

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

346213

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

add a comment |

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

346213

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

346213

answered Nov 29 '17 at 10:15

Rehan Sarwar

346213

answered Nov 29 '17 at 10:15

Rehan Sarwar

346213

answered Nov 29 '17 at 10:15

Rehan Sarwar

346213

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

add a comment |

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

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

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:

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

edited Jul 26 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

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:

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

edited Jul 26 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

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:

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

edited Jul 26 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

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 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

edited Jul 26 at 19:01

answered Jul 26 at 18:40

tomDev

2,91041828

answered Jul 26 at 18:40

tomDev

2,91041828

answered Jul 26 at 18:40

tomDev

2,91041828

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:

This string doesn't need translation

answered Sep 19 at 10:24

Harsh Masand

5614

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:

This string doesn't need translation

answered Sep 19 at 10:24

Harsh Masand

5614

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:

This string doesn't need translation

answered Sep 19 at 10:24

Harsh Masand

5614

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

answered Sep 19 at 10:24

Harsh Masand

5614

answered Sep 19 at 10:24

Harsh Masand

5614

answered Sep 19 at 10:24

Harsh Masand

5614

answered Sep 19 at 10:24

Harsh Masand

5614

add a comment |

You can find more info choosing assemble from gradle build tab: enter image description here

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

1

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 at 18:52

add a comment |

You can find more info choosing assemble from gradle build tab: enter image description here

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

1

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 at 18:52

add a comment |

You can find more info choosing assemble from gradle build tab: enter image description here

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

You can find more info choosing assemble from gradle build tab: enter image description here

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

answered Oct 3 at 9:51

Mateusz Kaflowski

490623

1

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 at 18:52

add a comment |

1

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 at 18:52

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 at 18:52

add a comment |

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

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

enter image description here

answered Feb 6 '15 at 5:11

Suranga

4,86062850

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 |

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

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

enter image description here

answered Feb 6 '15 at 5:11

Suranga

4,86062850

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 |

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

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

enter image description here

answered Feb 6 '15 at 5:11

Suranga

4,86062850

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

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

enter image description here

answered Feb 6 '15 at 5:11

Suranga

4,86062850

answered Feb 6 '15 at 5:11

Suranga

4,86062850

answered Feb 6 '15 at 5:11

Suranga

4,86062850

answered Feb 6 '15 at 5:11

Suranga

4,86062850

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 |

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

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.

answered Jun 7 '14 at 15:06

Eran Goldin

745916

add a comment |

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

answered Jun 7 '14 at 15:06

Eran Goldin

745916

add a comment |

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

answered Jun 7 '14 at 15:06

Eran Goldin

745916

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

answered Jun 7 '14 at 15:06

Eran Goldin

745916

answered Jun 7 '14 at 15:06

Eran Goldin

745916

answered Jun 7 '14 at 15:06

Eran Goldin

745916

answered Jun 7 '14 at 15:06

Eran Goldin

745916

add a comment |

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

  buildTypes {

        release {

            lintOptions {

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

answered Oct 30 at 6:14

Keshav Gera

2,4031727

add a comment |

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

  buildTypes {

        release {

            lintOptions {

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

answered Oct 30 at 6:14

Keshav Gera

2,4031727

add a comment |

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

  buildTypes {

        release {

            lintOptions {

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

answered Oct 30 at 6:14

Keshav Gera

2,4031727

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

  buildTypes {

        release {

            lintOptions {

                checkReleaseBuilds false

                abortOnError false

            }

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

answered Oct 30 at 6:14

Keshav Gera

2,4031727

answered Oct 30 at 6:14

Keshav Gera

2,4031727

answered Oct 30 at 6:14

Keshav Gera

2,4031727

answered Oct 30 at 6:14

Keshav Gera

2,4031727

add a comment |

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

answered Feb 18 '17 at 8:25

Kamal

7312

add a comment |

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

answered Feb 18 '17 at 8:25

Kamal

7312

add a comment |

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

answered Feb 18 '17 at 8:25

Kamal

7312

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

answered Feb 18 '17 at 8:25

Kamal

7312

answered Feb 18 '17 at 8:25

Kamal

7312

answered Feb 18 '17 at 8:25

Kamal

7312

answered Feb 18 '17 at 8:25

Kamal

7312

add a comment |

Try below code

buildTypes {

    release {

        lintOptions {

            disable 'MissingTranslation'

            checkReleaseBuilds false

            abortOnError false

        }

        minifyEnabled false

        signingConfig signingConfigs.release

    }

}

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

add a comment |

Try below code

buildTypes {

    release {

        lintOptions {

            disable 'MissingTranslation'

            checkReleaseBuilds false

            abortOnError false

        }

        minifyEnabled false

        signingConfig signingConfigs.release

    }

}

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

add a comment |

Try below code

buildTypes {

    release {

        lintOptions {

            disable 'MissingTranslation'

            checkReleaseBuilds false

            abortOnError false

        }

        minifyEnabled false

        signingConfig signingConfigs.release

    }

}

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

Try below code

buildTypes {

    release {

        lintOptions {

            disable 'MissingTranslation'

            checkReleaseBuilds false

            abortOnError false

        }

        minifyEnabled false

        signingConfig signingConfigs.release

    }

}

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

edited Oct 20 at 16:53

Sandy

1,4822721

edited Oct 20 at 16:53

Sandy

1,4822721

edited Oct 20 at 16:53

Sandy

1,4822721

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

answered Oct 20 at 15:21

Sheikh Ahmed Qureshi

add a comment |

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'

        }

    }

answered Nov 3 at 1:18

DoctorDroid Haiti

467

add a comment |

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'

        }

    }

answered Nov 3 at 1:18

DoctorDroid Haiti

467

add a comment |

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'

        }

    }

answered Nov 3 at 1:18

DoctorDroid Haiti

467

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'

        }

    }

answered Nov 3 at 1:18

DoctorDroid Haiti

467

answered Nov 3 at 1:18

DoctorDroid Haiti

467

answered Nov 3 at 1:18

DoctorDroid Haiti

467

answered Nov 3 at 1:18

DoctorDroid Haiti

467

add a comment |

If you add in app.gradle under android{

lintOptions {



    quiet true

    abortOnError false

}

}

It will get work

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

add a comment |

If you add in app.gradle under android{

lintOptions {



    quiet true

    abortOnError false

}

}

It will get work

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

add a comment |

If you add in app.gradle under android{

lintOptions {



    quiet true

    abortOnError false

}

}

It will get work

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

If you add in app.gradle under android{

lintOptions {



    quiet true

    abortOnError false

}

}

It will get work

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

answered Nov 22 at 17:38

Alpesh Sorathiya

22018

add a comment |

-1

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 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

add a comment |

-1

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 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

add a comment |

-1

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 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

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 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

edited Nov 11 at 19:21

Christian Gollhardt

9,488124372

edited Nov 11 at 19:21

Christian Gollhardt

9,488124372

edited Nov 11 at 19:21

Christian Gollhardt

9,488124372

answered Nov 11 at 19:02

Kaiffi

answered Nov 11 at 19:02

Kaiffi

answered Nov 11 at 19:02

Kaiffi

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Qfyilyi