Fixed
Status Update
No update yet.
Comments
tn...@google.com
As a workaround we added the following to our own manifest:
<provider
tools:replace="android:authorities"
android:name="com.google.android.gms.measurement.AppMeasurementContentProvider"
android:authorities="${applicationId}.google_measurement_service"
android:exported="false" />
You must have tools namespace defined in the xml.
<provider
tools:replace="android:authorities"
android:name="com.google.android.gms.measurement.AppMeasurementContentProvider"
android:authorities="${applicationId}.google_measurement_service"
android:exported="false" />
You must have tools namespace defined in the xml.
sp...@google.com
I've also been affected by this!
sp...@google.com
@2 I also opened an issue with tools guys https://code.google.com/p/android/issues/detail?id=193567 . I'm not really sure which team should fix it. There's another workaround there that in my opinion is cleaner.
[Deleted User] <[Deleted User]>
Comment has been deleted.
ru...@gmail.com
Comment has been deleted.
Description
Currently, with
android.lintOptions.textReport true, lint will output results to stdout when theAndroidLintTask(e.g.,lintDebug) runs, but there will be no such output if the task is up-to-date, which might mislead users to think that there are no lint issues.The desired behavior is for lint to output issues to stdout even if the task is up-to-date (or not to output anything if there are no issues - see
A possible fix would be to add a new lightweight task which would never be up-to-date and would only print the text report. I.e., change the lint build flow from this:
lintAnalyzeDebug->lintDebugto this:
lintAnalyzeDebug->lintReportDebug->lintDebugwhere the new
lintReportDebugtask is the oldlintDebugtask, and the newlintDebugis the lightweight task that is never up-to-date.Rejected alternative:
I considered modifying
AndroidLintCopyReportTaskto print out the text report, but that task will not run ifAndroidLintTaskis up-to-date. In fact, we can consider adding that task's functionality to the new lightweight lint task to properly fixPS - Thanks to Tor for noticing this issue :)