Status Update
No update yet.
Comments
gh...@google.com
je...@google.com
st...@google.com
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.
st...@google.com
Scott, assigning to you as it seem to complain the zip is not aligned while packaging which is very puzzling considering the steps...
da...@google.com
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
jo...@google.com
Not doing any post processing. No custom tasks. I will try to verify alignment now. Give me a sec.
da...@google.com
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"
jo...@google.com
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
AI-201.8743.12.41.7199119, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Linux(amd64) v5.11.0-18-generic, screens 5120x2880, 5120x2880
AS: 4.1.3; Kotlin plugin: 1.4.32-release-Studio4.1-1; Android Gradle Plugin: 4.1.3; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.6.2
We are using prefab to package a native-only library in a submodule of our project that is then referenced as a dependency of our main application module. We have found that the first build works fine but subsequent builds don't because, even though any changes get compiled into new shared object files, those shared object files aren't being packaged into the AAR. Instead, the stale asset is used and the new changes aren't reflected in the build.
Currently, we are using a workaround where we automatically delete the build/intermediates/prefab_package directory in a Gradle preBuild step. This seems to fix the problem, but shouldn't be necessary.