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
}
}
...
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhS358y-sXlLfchGl8z-Y4myqtzaJVloSUQvFkr6ZbX-nmWhilUVqruQwI9yL0D5r5dbZFZHrBk6TYmhlCTTJcNXnF_Dj53Tt8AlbZQNIUmEpo6A1xIsDM2tt8EJwGEu90WgeEiixUeng/s320/Screenshot+from+2018-08-11+20-58-01.png)
The message suggests to disable the lint checking but it would probably not be to your benefit to ignore the error.
After some digging around, I found that lint checking outputs a report which you can read to identify the source of the problem. The report can be found in the application's source build directory e.g. /your/Android/app/build/reports/ and named as lint-results-release-fatal.html
If you open up the report in a browser, the cause of the lint error can be easily seen. In this example, the reason for the compilation error is a missing language translation.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzTQKEZwNN2Y_2UJehQAI50NUMYi9PjnXjJBA7QD7uMcFQRb-xW-S4uY4SVFvLnbW5OzzlRNcMpol_LHwfeN2DHwE1H4SBt7f1JoRJTdK7ke2THsJ4yJokhs91zUUdKe8VNJUe-lUFiA/s320/Screenshot+from+2018-08-11+21-03-53.png)
1 comment:
Thank you :)
Post a Comment