Android Billing返回响应码5：重构代码后内购功能失效排查

Hey there! Let's break down why your in-app billing stopped working after refactoring for that addon adapter—since you’ve already ruled out manifest permissions and Play Console setup, we can focus on the refactoring-specific issues that usually trip folks up.

Common Refactoring Pitfalls to Check #

• IInAppBillingService Binding Timing Issues
  If you moved billing logic into your adapter, double-check that the service is fully bound before the adapter tries to use it. Services bind asynchronously, so if you initialize your adapter in onCreate() before onServiceConnected() fires, the adapter will get a null mService reference.
  Fix example: Initialize your adapter inside the onServiceConnected callback to ensure the service is ready:

  private ServiceConnection mServiceConn = new ServiceConnection() {
      @Override
      public void onServiceConnected(ComponentName name, IBinder service) {
          mService = IInAppBillingService.Stub.asInterface(service);
          // Initialize adapter only after service is connected
          mAddonAdapter = new AddonAdapter(AdOnsActivity.this, mService, mAddonList);
          mRecyclerView.setAdapter(mAddonAdapter);
      }
  
      @Override
      public void onServiceDisconnected(ComponentName name) {
          mService = null;
      }
  };
  

• Broken Product ID Passing
  When moving product ID management to the adapter, it’s easy to introduce typos or mismatches with the IDs configured in the Play Console. Add log statements to print the product IDs your adapter is passing to getSkuDetails() or launchPurchaseFlow()—confirm they match exactly (case-sensitive!) what’s in your Play Console setup.

• Disconnected Purchase Callbacks
  If your adapter initiates purchase requests, make sure the activity’s onActivityResult() is still forwarding results back to the billing logic. If you were using IabHelper, ensure the helper’s listener is properly attached, and that the adapter isn’t holding a stale reference to the activity (use a weak reference to avoid leaks and ensure callbacks fire correctly).

• Misplaced IabHelper Lifecycle
  If you’re using Google’s IabHelper, don’t initialize it inside the adapter—helpers are tied to the activity lifecycle. If you moved the helper to the adapter, it might get garbage collected early or fail to receive lifecycle events (like configuration changes). Keep the helper in the activity and pass it to the adapter, or use a callback interface to let the activity handle billing operations.

• Missing Error Handling
  Refactoring often strips out old error logging. Add logs to catch service binding failures (bindService() returns false?), sku detail query errors, or purchase flow exceptions. This will help you pinpoint exactly where the billing flow is breaking.

内容的提问来源于stack exchange，提问作者rootmeanclaire