Skip to main content
Solved

Build error: minifyReleaseWithR8 failing with purchases_flutter (FlutterFlow user)

  • October 23, 2026
  • 2 replies
  • 25 views
Forum|alt.badge.img+1

Hi RevenueCat team and community, I am building my mobile application using FlutterFlow (No-Code platform), so I do not manually manage native Android configuration files or code in a standard IDE. When trying to generate a release Android App Bundle (AAB), my build fails during the R8 minification task because of `purchases_flutter` and Google Play Billing API classes. I have attached a complete diagnostic report to this post (Flutter Build Diagnostic Report.pdf) which contains the exact error logs, but here is the core issue:

ERROR: R8: Missing class com.android.billingclient.api.QueryPurchaseHistoryParams$Builder (referenced from: ... com.revenuecat.purchases.google.BillingClientParamBuildersKt.buildQueryPurchaseHistoryParams(...)) Execution failed for task ':app:minifyReleaseWithR8'.

Since I am working within FlutterFlow, could you please advise on how I can resolve this? Specifically: 1. Do I need to add custom ProGuard keep rules in FlutterFlow for RevenueCat / Google Play Billing? 2. Is there a recommended configuration to prevent R8 from stripping these classes in a FlutterFlow project? Thank you so much for your help!

Best answer by Crudyg123

Are you using FlutterFlow’s built-in RevenueCat integration, and have you added any custom packages to your project?

View original

    2 replies

    Forum|alt.badge.img+5
    • Crudyg123
    • Active Helper
    • Answer
    • October 23, 2026

    Are you using FlutterFlow’s built-in RevenueCat integration, and have you added any custom packages to your project?

      Forum|alt.badge.img+1
      • help
      • Author
      • New Member
      • October 23, 2026

      Hi @Crudyg123,

      Thanks for following up! The issue is completely resolved now.

      The release build was failing during R8 minification because the Google Play Billing API classes were being stripped out. 

      Adding these custom ProGuard rules in FlutterFlow (`proguard-rules.pro`) fixed the problem and the AAB build completed successfully:

      -keep class com.android.billingclient.api.** { *; }
      -dontwarn com.android.billingclient.api.**

      Thank you again for your assistance!

        Terms & ConditionsAccessibility statement