Add variant-specific manifests to resolve googlePlay manifest merge conflicts

[Copilot]

Manifest merge fails in :app:processGooglePlayDebugUnitTestManifest due to conflicting application@allowBackup, application@dataExtractionRules, and application@fullBackupContent attributes between com.reown:sign:1.4.12 and com.appsflyer:af-android-sdk:6.17.3.

Changes

Added variant-specific manifests for all googlePlay build variants with explicit tools:replace directives:

• app/src/googlePlay/AndroidManifest.xml
• app/src/googlePlayDebug/AndroidManifest.xml
• app/src/googlePlayStaging/AndroidManifest.xml
• app/src/googlePlayRelease/AndroidManifest.xml

Each manifest declares the conflicting attributes with values matching the main manifest and instructs the merger to use these values:

<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools"> <application android:allowBackup="false" android:dataExtractionRules="@xml/backup_config" android:fullBackupContent="false" tools:replace="android:allowBackup,android:dataExtractionRules,android:fullBackupContent" /> </manifest>

The main manifest's tools:replace doesn't apply during unit test manifest merging, requiring these variant-specific overrides.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dl.google.com
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED --add-opens=java.base/java.time=ALL-UNNAMED -XX:+UseParallelGC -Xmx10g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-9.2.0-bin/11i5gvueggl8a5cioxuftxrik/gradle-9.2.0/lib/gradle-daemon-main-9.2.0.jar -javaagent:/home/REDACTED/.gradle/wrapper/dists/gradle-9.2.0-bin/11i5gvueggl8a5cioxuftxrik/gradle-9.2.0/lib/agents/gradle-instrumentation-agent-9.2.0.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 9.2.0 (dns block)
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java -XX:+UseParallelGC --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED -Xmx10g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-8.9-bin/90cnw93cvbtalezasaz0blq0a/gradle-8.9/lib/gradle-daemon-main-8.9.jar -javaagent:/home/REDACTED/.gradle/wrapper/dists/gradle-8.9-bin/90cnw93cvbtalezasaz0blq0a/gradle-8.9/lib/agents/gradle-instrumentation-agent-8.9.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.9 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Failure: CI job failed at task :app:processGooglePlayDebugUnitTestManifest due to manifest merge conflicts between com.reown:sign:1.4.12 and com.appsflyer:af-android-sdk:6.17.3. Conflicting attributes: application@dataExtractionRules and application@fullBackupContent (also android:allowBackup). The test/variant manifest merge needs a tools:replace override for the googlePlayDebug variant and its unit-test merge.

Goal: Add variant-specific manifest(s) that apply tools:replace on the tag so the manifest merger uses the values from the app and avoids conflicts from dependencies.

Changes to add in repository MixinNetwork/android-app:

1. Add file: app/src/googlePlayDebug/AndroidManifest.xml

Contents (exact):

2. Add file: app/src/googlePlayDebugTest/AndroidManifest.xml

Contents (exact):

Notes:

• If you prefer a different value for fullBackupContent, set android:fullBackupContent accordingly.
• The repo already had a tools:replace on the main manifest; the failure occurred in the googlePlayDebug unit-test merge, so adding variant+test manifests fixes the merge for the failing task.
• Branch/PR: create a branch named fix/manifest-merge-googlePlayDebug and open a PR with these two files added and a short description linking to the failing CI job. Use commit message: "fix: add googlePlayDebug variant manifests to override backup/dataExtractionRules conflicts".

Please create the pull request that adds these two files and opens it against the default branch. Include a short PR description referencing the failing job (job id: 55678234975, job ref: 3387ed0).

This pull request was created as a result of the following prompt from Copilot chat.

Failure: CI job failed at task :app:processGooglePlayDebugUnitTestManifest due to manifest merge conflicts between com.reown:sign:1.4.12 and com.appsflyer:af-android-sdk:6.17.3. Conflicting attributes: application@dataExtractionRules and application@fullBackupContent (also android:allowBackup). The test/variant manifest merge needs a tools:replace override for the googlePlayDebug variant and its unit-test merge.

Goal: Add variant-specific manifest(s) that apply tools:replace on the tag so the manifest merger uses the values from the app and avoids conflicts from dependencies.

Changes to add in repository MixinNetwork/android-app:

1. Add file: app/src/googlePlayDebug/AndroidManifest.xml

Contents (exact):

2. Add file: app/src/googlePlayDebugTest/AndroidManifest.xml

Contents (exact):

Notes:

• If you prefer a different value for fullBackupContent, set android:fullBackupContent accordingly.
• The repo already had a tools:replace on the main manifest; the failure occurred in the googlePlayDebug unit-test merge, so adding variant+test manifests fixes the merge for the failing task.
• Branch/PR: create a branch named fix/manifest-merge-googlePlayDebug and open a PR with these two files added and a short description linking to the failing CI job. Use commit message: "fix: add googlePlayDebug variant manifests to override backup/dataExtractionRules conflicts".

Please create the pull request that adds these two files and opens it against the default branch. Include a short PR description referencing the failing job (job id: 55678234975, job ref: 3387ed0).

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull Request Overview

This PR addresses manifest merge conflicts during unit test execution by adding a test-specific manifest with explicit conflict resolution directives. The conflicts arose between dependencies com.reown:sign:1.4.12 and com.appsflyer:af-android-sdk:6.17.3 over backup-related attributes.

• Added a unit test manifest with tools:replace directives to resolve attribute conflicts
• Configured Robolectric SDK versions for unit tests
• Updated build configuration to reference the test manifest

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
app/src/test/AndroidManifest.xml	New test manifest declaring conflicting attributes with tools:replace directives to resolve manifest merge conflicts
app/build.gradle	Added Robolectric configuration and test manifest source set (contains duplicate sourceSets block that needs merging)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Duplicate sourceSets block detected. There's already a sourceSets block at line 91 that configures test source directories. The new manifest configuration should be added to that existing block rather than creating a second sourceSets block. Gradle will only use one of these blocks, which could lead to unexpected behavior.

Suggestion: Merge this into the existing sourceSets block (lines 91-100) like this:

sourceSets { String sharedTestDir = 'src/sharedTest/java' test { java.srcDirs += sharedTestDir manifest.srcFile 'src/test/AndroidManifest.xml' } androidTest { java.srcDirs += sharedTestDir assets.srcDirs += files("$projectDir/schemas".toString()) } }

Suggested change

	sourceSets {
	test {
	manifest.srcFile 'src/test/AndroidManifest.xml'
	}
	}
	// Merged test manifest configuration into the main sourceSets block above (lines 91-100).

[Copilot]

[nitpick] There appear to be trailing whitespace characters on the blank lines inside the <application> tag (lines 10 and 15). Consider removing these for consistency with typical XML formatting.

Suggested change

	<meta-data
	android:name="com.google.mlkit.vision.DEPENDENCIES"
	android:value="(barcode)"
	tools:replace="android:value" />
	<meta-data
	android:name="com.google.mlkit.vision.DEPENDENCIES"
	android:value="(barcode)"
	tools:replace="android:value" />