CopyPastor

Detecting plagiarism made easy.

Score: 0.8357534789101259; Reported for: String similarity Open both answers

Possible Plagiarism

Plagiarized on 2022-08-12
by Ahmed Nabil

Original Post

Original - Posted on 2020-08-11
by Umair



            
Present in both answers; Present only in the new answer; Present only in the old answer;

The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs: https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d
according to this [github issue][1]
this is the solution :
lintOptions { checkReleaseBuilds false }

[1]: https://github.com/flutter/flutter/issues/58247
The Android Gradle LintPerVariantTask now appears to be adding JARs from all build variants to its inputs: https://android.googlesource.com/platform/tools/base/+/1f9787310d64a66370627a2aaefa1e616565c17d
The libapp.so libraries containing the app's compiled Dart code are packaged in a JAR, and a different JAR is generated for each variant. I'm not sure how dynamically generated per-variant JARs are supposed to be handled if the lint task expects all variants' JARs to be available.
As a hack workaround you could change the lintOptions in **app/build.gradle** to disable the lint task:
lintOptions { checkReleaseBuilds false }

        
Present in both answers; Present only in the new answer; Present only in the old answer;