Android AAB packaging conflict: utopia-sdk (libagnos.so) cannot coexist with Stripe Tap to Pay in a single app

[ansi-code]

Summary

com.sumup.tap-to-pay:utopia-sdk cannot be packaged in the same Android App Bundle with another Tap to Pay SDK (Stripe Terminal Tap to Pay) because both include libagnos.so with different binary content.
This blocks a single-app architecture where users choose the provider at runtime.

Steps to Reproduce

1. Add these dependencies:

dependencies {
  implementation("com.sumup:merchant-sdk:6.0.0")
  implementation("com.sumup.tap-to-pay:utopia-sdk:1.0.6")

  implementation("com.stripe:stripeterminal-taptopay:5.2.0")
  implementation("com.stripe:stripeterminal-core:5.2.0")
}

2. Build Android App Bundle:

./gradlew :app:bundleDebug

Expected Behavior

The app bundle is generated successfully, allowing a single app to support both providers (only one active at runtime).

Actual Behavior

Build fails at bundle packaging:

Execution failed for task ':app:packageDebugBundle'.
A failure occurred while executing com.android.build.gradle.internal.tasks.PackageBundleTask$BundleToolWorkAction
Modules 'feature_stripe' and 'feature_sumup' contain entry 'lib/arm64-v8a/libagnos.so' with different content.

Android Version(s)

Observed at build/package time (AAB), so not tied to a specific runtime Android version.
Project config: minSdk 29, targetSdk 36, compileSdk 36.

Impacted Devices

Not device-specific (build-time issue before install/runtime).

Impacted Readers

Not reader-specific (build-time issue before reader connection).

Firmware Version(s)

N/A (issue occurs before runtime/reader usage).

Crash Log

N/A (no app/runtime crash, this is a Gradle bundle packaging failure).

Dependency Versions

• SumUp SDK: com.sumup:merchant-sdk:6.0.0, com.sumup.tap-to-pay:utopia-sdk:1.0.6
• Kotlin: 2.2.20 (plugin), stdlib forced to 2.2.20
• Android Gradle Plugin: 8.13.2
• Gradle: 8.13

Video / Screenshot

Not attached yet. I can provide build output screenshots and a minimal repro project if needed.

Other Information

• I tested multiple SumUp Tap to Pay versions and compared AGNOS native hashes against Stripe Tap to Pay versions programmatically.
• No compatible binary pair found (libagnos.so differs).
• pickFirst, excludes, R8/proguard, dynamic features, and separate process do not provide a clean/supported fix for one app bundle.
• Request: is there an official SumUp-supported way to coexist with another Tap to Pay SDK in one app (for example, alternative artifact/packaging strategy for AGNOS, or a compatibility matrix)?

[DmBard]

Hello @ansi-code,

Thank you for providing the detailed feedback regarding the packaging conflict between the SumUp Tap to Pay SDK and the Stripe Terminal SDK.

We’ve reviewed the issue where both SDKs include libagnos.so with different binary content. At this stage, the SumUp Tap to Pay SDK was not designed to coexist with other SoftPOS SDKs within a single application bundle, which is why you are encountering this packaging failure.

We have created an internal ticket to investigate the possibility of renaming these libraries to resolve the conflict. However, for the next several quarters, our primary focus remains on ensuring reliable transaction acceptance across all supported devices and expanding our feature set in various global markets.
While we have logged this feedback for future planning, we do not currently have a timeline for when a fix for this specific architectural conflict will be implemented.

Possible workaround
To avoid the conflict you can use the different product flavours but I am not sure that it suits your needs.

For future reference, while this issue was opened in the Android Reader SDK GitHub, these types of architectural blockers are best flagged directly to our Integrations Team. This ensures they reach the correct engineers and product managers immediately.

We appreciate your patience and the feedback as it helps us understand how our integrators are evolving their app architectures.

[leila-sumup]

Thanks for the detailed report, @ansi-code. As @DmBard noted above, packaging both SDKs in a single app bundle is not currently supported, and we don't have a timeline for a fix at this stage.

We'll close this issue for now. If you'd like to stay updated on this use case or discuss alternative approaches, please reach out directly to our integrations team at integration@sumup.com