Status Update
Comments
uc...@google.com <uc...@google.com>
ga...@google.com <ga...@google.com>
sp...@google.com <sp...@google.com> #2
Okay. I tried a bunch of agp+android studio versions
The last working version was classpath("com.android.tools.build:gradle:7.4.0-alpha06")
once I moved to
classpath("com.android.tools.build:gradle:7.4.0-alpha07")
then things start breaking on firebase app dist.
pa...@gmail.com <pa...@gmail.com> #3
Scott, assigning to you as it seem to complain the zip is not aligned while packaging which is very puzzling considering the steps...
da...@gmail.com <da...@gmail.com> #4
OP, when you build the APK with AGP, are you doing any post-processing on the APK and/or do you have any custom tasks that are modifying the APK?
Can you try to verify the alignment of your APK with zipalign
locally (zipalign
is included in build-tools
):
zipalign -c -v 4 foo.apk
ts...@vewd.com <ts...@vewd.com> #5
Not doing any post processing. No custom tasks. I will try to verify alignment now. Give me a sec.
pa...@gmail.com <pa...@gmail.com> #6
Scenario 1:
built my apk with agp alpha09, but didn't update firebase (bom = 30.2.0)
/Users/idle/Library/Android/sdk/build-tools/31.0.0/zipalign -c -v 4 app-release.apk
"Verification succesful"
Scenario 2:
built my apk with agp alpha09, but I DID update firebase (bom = 30.3.1)
/Users/idle/Library/Android/sdk/build-tools/31.0.0/zipalign -c -v 4 app-release.apk
"Verification FAILED"
sp...@google.com <sp...@google.com> #7
Scenario 3:
built my apk with agp alpha09, with androidx.splash rc01
/Users/idle/Library/Android/sdk/build-tools/31.0.0/zipalign -c -v 4 app-release.apk
"Verification succesful"
Scenario 4:
built my apk with agp alpha09, with androidx.splash 1.0.0
/Users/idle/Library/Android/sdk/build-tools/31.0.0/zipalign -c -v 4 app-release.apk
"Verification FAILED"
In both failed cases if I do | grep BAD
I get
7216334 junit/runner/logo.gif (BAD - 2)
7217354 junit/runner/smalllogo.gif (BAD - 2)
Description
DESCRIBE THE ISSUE IN DETAIL:
It is possible to put
lint.xml
s in therootProject
and in every module individually. These will be considered together to set up configuration for each module. In the attach project the structure is:app
lint.xml
missing, will use../lint.xml
lib
lint.xml
exists, but empty (will be modified by step 6)lint.xml
exists, and suppresses the clear unused resources by pattern.STEPS TO REPRODUCE:
gradlew lint
:lib:lintDebug
telling us there's an unused resource called "unused" inlib/build/reports/lint-results-debug.html
gradlew lint
lib/lint.xml
and uncomment<ignore>
gradlew lint
Actual: Observe nothing was executed, everything up-to-date.
Expected: lint analysis re-executes and updates the HTML report with the findings based on the newly changed config file.
Bonus steps to prove that the uncommenting should have an effect:
gradlew clean lint --no-build-cache
Workaround
polyfill missing setup