Google Play DEX Optimization Requirements Conflict with Mobile Payments SDK

Hi Square Team,

Google Play has introduced new DEX code optimization requirements, requiring apps to meet a minimum 25% threshold for obfuscation, shrinking, and optimization starting in February 2027.

Our Android app uses the Square Mobile Payments SDK, and Google Play Console is already showing the following warning:

DEX code optimization is below our threshold.
Obfuscation: 2%

Percentages under 25% may impact app visibility and publishing capabilities on Google Play.

However, the Square Mobile Payments SDK documentation states that ProGuard code optimization is not supported, and the SDK integration requires us to disable minification (minifyEnabled = false).

This creates a conflict between Google’s upcoming requirements and Square’s SDK integration guidelines.

Could the Square team clarify the following?

  1. Are there plans to officially support R8/ProGuard minification and optimization before February 2027?

  2. Will Square provide official ProGuard/R8 rules to safely enable code optimization?

  3. Is there a recommended workaround that allows apps using the Mobile Payments SDK to meet Google’s requirements without affecting payment functionality?

Since this may impact our ability to publish future Android app updates, we would appreciate an official recommendation or roadmap.

Google documentation:

Thanks!

This is a critical conflict for Android developers using the SDK! Hopefully Square provides official R8 rules soon, otherwise many apps face publishing blocks once February 2027 arrives. MyMilestoneCard login

Hi @LukeChen thanks for flagging this. You’re right to raise the conflict between Google’s February 2027 requirements and our current Android Mobile Payments SDK guidance.

I don’t have a confirmed supported workaround or release timeline to share. We also can’t recommend enabling R8 with generic keep rules as a production solution without confirmation that the configuration preserves payment functionality.

In the meantime, please continue following the published SDK guidance for production releases; we don’t want to suggest an unvalidated configuration for payment processing.

Hi, thanks for your response and for escalating this to the team.

Here are the details from our Android build:

  • Mobile Payments SDK: 2.6.1

  • Android Gradle Plugin: 9.2.1

  • Total uncompressed DEX size: 142 MB

  • Shrinking: N/A (shown as “-” in Play Console)

  • Optimization: N/A (shown as “-” in Play Console)

  • Obfuscation: 2%

We’re currently following Square’s official guidance and keeping R8 disabled (minifyEnabled = false) to avoid potential payment issues.

We’d appreciate any updates on this, as it affects production apps relying on the Mobile Payments SDK.

Thanks again for your help!

watching.

We have the same issue. While we have minifyEnabled = true and R8 enabled, our percentages are still below 25%.

  • Obfuscation (19%)
  • Shrinking (19%)
  • Optimisation (19%)

Our .NET for Android app will have this issue too.