IssueTracker

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.

Scott, assigning to you as it seem to complain the zip is not aligned while packaging which is very puzzling considering the steps...

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

Not doing any post processing. No custom tasks. I will try to verify alignment now. Give me a sec.

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"

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)

In the cases where zipalign verification fails, is the APK generated by a clean build (e.g., ./gradlew clean :app:assembleRelease)?

Does verification succeed if you add this to your build.gradle?

android {
    packagingOptions {
        exclude 'junit/runner/logo.gif'
        exclude 'junit/runner/smalllogo.gif'
    }
}

In the cases where zipalign verification fails, is the APK generated by a clean build (e.g., ./gradlew clean :app:assembleRelease)?

I clean before i generate the apk using the Android Studio menu for generating an apk

Does verification succeed if you add this to your build.gradle?

I assume it will, but let me try. Any reason why changing from androidx.splash 1.0.0-rc01 to 1.0.0 stable (which is 0 changes. all it changed was the dependency version) that it fails verification. It seems like something else is wrong that's a bit deeper than just adding these two exclude statements.

It seems like something else is wrong that's a bit deeper than just adding these two exclude statements.

I agree, but I'd like to find a workaround for you in the meantime.

I think I'll probably need a repro project to get to the bottom of it. In your other thread, it sounded like you weren't able to create a repro project... any luck since then?

I was not able to create a repro unfortunately. As soon as I started to prune things out of my project it started to succeed.

Similarly. firebase came out with a new version. and if i use that new version... then it also succeeds. 🤯

I'm glad to hear there is a workaround for now (and i learned something new about zipalign). I will try to create a repo project again later today when I have about an hour or so free to play around with it, but for now I will just commit the

android {
    packagingOptions {
        exclude 'junit/runner/logo.gif'
        exclude 'junit/runner/smalllogo.gif'
    }
}

to my codebase because that did the trick for me. Everything works. Thank you for your quick response and helpful debugging steps.

Thanks!

not able to get a repro case. literally any minor thing i change makes this verify successfully. im a bit out of ideas. the only thing i can think of that might help is why is junit being packaged into my app.

and i think the reason for that is that I depend on okhttp3:mockwebserver:4.10.0

implementation("junit:junit:4.13.2") // Needed because mockwebserver has a dependency on it. This can be removed in okhttp 5+

so the apps i ship through firebase have a mockwebserver using okhttpmockwebserver, but version 4+ requires junit while okhttp 5+ (not yet released), removes this dep.

so maybe just playing around with adding junit as a dependency to an actual app might help repro?

source: https://github.com/square/okhttp/issues/7249#issuecomment-1105109861

maybe still owrth checking out as there could be other deps that end up with the same issue. idk. just trying to be helpful i guess. but as for me. im going to consider this case closed. excluding the above like you mentioned has unblocked my team. cheers

Thanks for looking into it!

I agree it's strange they have an implementation dependency on junit, and I'm glad they're removing it in okhttp 5+.

I'll go ahead and close this bug for now.

This is fixed by Change-Id: I12ec8785cd4dbb6e523c66b4620ed2388f448822, which will be in AGP 7.4.0-rc01 and 8.0.0-alpha08.

Thanks for filing the bug, OP. Your observation in comment #2 that alpha07 was the first broken version helped me find the root cause.

FUCK YEAH! Glad I was helpful! Appreciate you working through it with me here. Cheers. Once I update to alpha08 I will remove the workaround I added. cheers

I'm also have this same error with zoom in flutter

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:shrinkReleaseRes'.
> Multiple task action failures occurred:
   > A failure occurred while executing com.android.build.gradle.internal.transforms.ShrinkProtoResourcesAction
      > ParseError at [row,col]:[1,1]
        Message: Content is not allowed in prolog.
   > A failure occurred while executing com.android.build.gradle.internal.transforms.ShrinkProtoResourcesAction
      > ParseError at [row,col]:[1,1]
        Message: Content is not allowed in prolog.
   > A failure occurred while executing com.android.build.gradle.internal.transforms.ShrinkProtoResourcesAction
      > ParseError at [row,col]:[1,1]
        Message: Content is not allowed in prolog.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6m 28s
Running Gradle task 'assembleRelease'...                          389.5s
Gradle task assembleRelease failed with exit code 1

zoom_native_sdk: ^0.3.3

Flutter 3.10.5 • channel stable • https://github.com/flutter/flutter.git Framework • revision 796c8ef792 (4 weeks ago) • 2023-06-13 15:51:02 -0700 Engine • revision 45f6e00911 Tools • Dart 3.0.5 • DevTools 2.23.1

java version "17.0.7" 2023-04-18 LTS Java(TM) SE Runtime Environment (build 17.0.7+8-LTS-224) Java HotSpot(TM) 64-Bit Server VM (build 17.0.7+8-LTS-224, mixed mode, sharing)

Gradle 7.6.1

Build time: 2023-02-24 13:54:42 UTC Revision: 3905fe8ac072bbd925c70ddbddddf4463341f4b4

Kotlin: 1.7.10 Groovy: 3.0.13 Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021 JVM: 17.0.7 (Oracle Corporation 17.0.7+8-LTS-224) OS: Windows 11 10.0 amd6

Manually updating the .xml files to not have a BOM should be a way to workaround this issue. Most text editors have a way of saving without a BOM.