User Choice billing only working in Dev client

[singhayush1403]

I've been implementing the user choice billing flow for google play. During development, the options show up correctly to choose between google play and my payment method, but while testing a release app it directly takes to me google play options and does not allow me to choose. I can see in the native logs that the library has been initialized the same way in both cases.
Dependencies:
"react-native-iap": "^14.5.0"
"react-native": "0.79.2"

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Subscription Upgrade Issue- CHARGE_PRORATED_PRICE Not Working. #2940
• Error: Google is indicating that we have some issue connecting to payment. #2979
• How to modify the replacementModeAndroid of the base plan? #2933
• Discounted offer from Google Play not applied (one-time product) #3102
• App crashes on upgrade to latest version of android billing. #2961

👤 Suggested Assignees

• Nikhil-MathBud
• ashok1607
• David-LJQ
• arechsteiner
• ad77076

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Approach

The ticket addresses a critical issue where User Choice Billing dialog works correctly in development builds but fails to appear in release builds, defaulting directly to Google Play billing. The fix involves adding the com.android.vending.BILLING permission to the library's AndroidManifest.xml to ensure it propagates to all consumer applications, and updating documentation to provide clarity on permission handling and troubleshooting guidance for release build issues.

Observations

This is a React Native IAP library (react-native-iap) built with Nitro modules, providing a bridge between JavaScript and native Android/iOS billing APIs. The Android implementation uses the OpenIAP library wrapper to interface with Google Play Billing. The library includes TypeScript API layers (src/), Android native code (android/), documentation (docs/), and example applications. User Choice Billing is configured through initConnection() with alternativeBillingModeAndroid parameter and uses event listeners to handle billing choices.

The exploration revealed that none of the AndroidManifest.xml files in the repository declare the com.android.vending.BILLING permission, which is required for Google Play Billing functionality. While the OpenIAP dependency may include this permission in its own manifest, manifest merging in release builds may not reliably propagate it to the final APK.

Assumptions

Assumption 1: Why does User Choice Billing work in debug but not release builds?

Options Considered:

• Document that users must manually add the permission to their app manifest
• Add the permission to the library's manifest so it propagates automatically
• Add permission to library manifest AND update documentation

Chosen Option: Add permission to library manifest AND update documentation

Rationale: This approach fixes the issue automatically for all users (aligning with the library's documented claim that permissions are "automatically handled") while also providing clear guidance for troubleshooting. This is the most developer-friendly solution as it requires no manual configuration from library consumers.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Add Required Billing Permission to Library Manifest

Update the library's Android manifest to explicitly declare the required billing permission, ensuring it propagates to all consumer applications through manifest merging.

Add BILLING Permission Declaration

Add the com.android.vending.BILLING permission to android/src/main/AndroidManifest.xml

• Insert <uses-permission android:name="com.android.vending.BILLING" /> as a direct child of the <manifest> root element
• This ensures the permission is automatically merged into any consumer app that includes the library
• The permission enables Google Play Billing functionality including User Choice Billing flows in all build variants

🤖 Prompt for AI agents

This phase adds the required billing permission to ensure User Choice Billing
works in release builds.

In android/src/main/AndroidManifest.xml:
- Add `<uses-permission android:name="com.android.vending.BILLING" />` as a
direct child of the `<manifest>` root element
- This ensures the permission propagates to consumer applications through
manifest merging

Phase 2: Update Documentation for Clarity and Troubleshooting

Enhance documentation to clarify permission requirements and provide specific troubleshooting guidance for release build issues.

Task 1: Update Troubleshooting Guide

Modify docs/docs/guides/troubleshooting.md to add a dedicated section for release build issues

• Add a new subsection under Android troubleshooting titled "User Choice Billing Not Showing in Release Builds"
• Explain that the library now includes the BILLING permission automatically, but provide verification steps for developers experiencing issues
• Include instructions for verifying the merged manifest in release builds (using Android Studio's "Analyze APK" or gradle's manifest merger report)
• Add guidance on checking that no manifest merger rules are removing the permission

Task 2: Clarify Setup Documentation

Update docs/docs/getting-started/setup-android.md to explicitly mention permission handling

• Add a brief note in the automatic configuration section confirming that the BILLING permission is included in the library manifest
• For users experiencing issues, reference the troubleshooting guide
• This provides reassurance while maintaining the simplicity of the setup process

Task 3: Update Alternative Billing Guide

Enhance docs/docs/guides/alternative-billing.md with release build considerations

• Add a subsection under "Testing" about verifying User Choice Billing in release builds
• Include common issues specific to release builds (such as ProGuard configuration being correct but permission missing)
• Reference the troubleshooting guide for detailed debugging steps

🤖 Prompt for AI agents

This phase updates documentation to clarify permission handling and provide
troubleshooting guidance for release build issues.

In docs/docs/guides/troubleshooting.md:
- Add subsection "User Choice Billing Not Showing in Release Builds" under
Android troubleshooting
- Explain automatic BILLING permission inclusion and provide verification steps
- Include instructions for checking merged manifest in release builds
- Add guidance on manifest merger rules

In docs/docs/getting-started/setup-android.md:
- Add note in automatic configuration section confirming BILLING permission is
included
- Reference troubleshooting guide for issues

In docs/docs/guides/alternative-billing.md:
- Add subsection under "Testing" for verifying User Choice Billing in release
builds
- Document common release build issues
- Reference troubleshooting guide

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

This phase adds the required billing permission to ensure User Choice Billing
works in release builds.

In android/src/main/AndroidManifest.xml:
- Add `<uses-permission android:name="com.android.vending.BILLING" />` as a
direct child of the `<manifest>` root element
- This ensures the permission propagates to consumer applications through
manifest merging
===============================================================================

Task: 2

This phase updates documentation to clarify permission handling and provide
troubleshooting guidance for release build issues.

In docs/docs/guides/troubleshooting.md:
- Add subsection "User Choice Billing Not Showing in Release Builds" under
Android troubleshooting
- Explain automatic BILLING permission inclusion and provide verification steps
- Include instructions for checking merged manifest in release builds
- Add guidance on manifest merger rules

In docs/docs/getting-started/setup-android.md:
- Add note in automatic configuration section confirming BILLING permission is
included
- Reference troubleshooting guide for issues

In docs/docs/guides/alternative-billing.md:
- Add subsection under "Testing" for verifying User Choice Billing in release
builds
- Document common release build issues
- Reference troubleshooting guide

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[hyochan]

This behavior is expected and related to Google Play Console configuration, not a library issue.

Why it works in dev but not release

Google Play's development environment may not enforce all restrictions. In production, Google enforces:

• App enrollment status in Play Console
• Regional eligibility (user's Google Play account country)
• App type (gaming vs non-gaming)

Please verify

1. Is your app enrolled?

   • Go to Play Console > Settings > Alternative billing
   • Ensure your app is opted-in for user choice billing

2. Which country are you testing in?

   • User choice billing only works in eligible countries:
     • EEA: gaming & non-gaming apps
     • South Korea, India, Japan, Brazil, Australia, UK, etc.: non-gaming apps only

3. Is this a gaming app?

   • Games can only use user choice billing in the EEA

4. Release build configuration

   • Verify your release build includes:

   await initConnection({
     alternativeBillingModeAndroid: 'user-choice',
   });

References

• Understanding user choice billing on Google Play
• Enrolling in the user choice billing pilot
• In-app integration guidance for alternative billing

[singhayush1403]

@hyochan We are using it for a non gaming app. The setup is complete in the play console dashboard and I am initializing the connection in the same way as you have mentioned. Only after doing all this, the user choice billing started displaying in the debug app as well.

[hyochan]

Since your setup is complete and it works in debug, this appears to be a Google Play configuration issue rather than a library issue.

The library simply passes alternativeBillingModeAndroid: 'user-choice' to the Google Play Billing SDK - whether the choice dialog appears is entirely controlled by Google Play based on your app's enrollment status and the user's eligibility.

I recommend contacting Google Play Developer Support directly:

• Google Play Developer Support

They can verify your app's enrollment status and troubleshoot why User Choice Billing isn't being triggered in production.

When contacting them, include:

• Your app's package name
• The testing track you're using
• The country of your test account
• Screenshots showing your Alternative Billing settings in Play Console

If you find a solution, please share it here for others who may encounter the same issue.