[Android] purchaseUpdatedListener firing only once, not on every subscription transaction

[mzablockifm]

Version of react-native-iap

"react-native-iap": "4.5.4",

Version of react-native

"react-native": "0.61.4",

Platforms you faced the error (IOS or Android or both?)

Android, not tested on iOS

Expected behavior

purchaseUpdatedListener firing every time purchase is received

Actual behavior

purchaseUpdatedListener firing only once for first recipt, then nothing happens

Tested environment (Emulator? Real Device?)

Real device, run in dev env with test google account (subscription recurring every 5 minutes - email is incoming but receipt is not).

Simplified code I am using:

import React from 'react';
import { Text, View, TouchableOpacity, Alert } from 'react-native';
import RNIap, {
  purchaseUpdatedListener,
  purchaseErrorListener,
} from 'react-native-iap';

import { SpinnerOverlay } from '../components/SpinnerOverlay';

import { itemSkus } from '../config/in-app';
import { validateRecipt } from '../utils/validateRecipt';
import { logger } from '../utils/logger';

export class SubscriptionScreenInner extends React.Component {
  purchaseUpdateSubscription = null;
  purchaseErrorSubscription = null;

  constructor(props) {
    super(props);
    this.state = {
      products: [],
      productsLoaded: false,
      isProcessing: false
    };
  }

  componentDidMount = async () => {
    try {
      if (itemSkus) {
        await RNIap.initConnection();
        await RNIap.flushFailedPurchasesCachedAsPendingAndroid();
        const products = await RNIap.getSubscriptions(itemSkus);
        this.setState({ products, productsLoaded: true });

        this.purchaseUpdateSubscription = purchaseUpdatedListener(
          async (purchase) => {
            try {
              const receipt = purchase.transactionReceipt;
              if (receipt) {
                const validate = await validateRecipt(purchase);

                if (validate) {
                  await RNIap.finishTransaction(purchase, false);
                  this.props.fetchUserProfile();
                  this.resetScreenState();
                  Alert.alert('receipt validated', 'cool');
                }
              }
            } catch (error) {
              this.resetScreenState();
              logger('Validate recipt error', error);
            }
          }
        );

        this.purchaseErrorSubscription = purchaseErrorListener((error) => {
          this.resetScreenState();
          logger('Purchase error during loading', error);
        });
      }
    } catch (error) {
      logger('Store prroducts error', error);
    }
  };

  componentWillUnmount() {
    if (this.purchaseUpdateSubscription) {
      this.purchaseUpdateSubscription.remove();
    }

    if (this.purchaseErrorSubscription) {
      this.purchaseErrorSubscription.remove();
    }

    RNIap.endConnection();
  }

  requestSubscription = async (sku) => {
    this.setState({ isProcessing: true }, async () => {
      await RNIap.requestSubscription(sku);
    });
  };

  resetScreenState = () => {
    this.setState({ isProcessing: false });
  };

  render() {
    const { products, productsLoaded, isProcessing } = this.state;

    if (!productsLoaded || isProcessing) {
      return (
        <View>
          <SpinnerOverlay />
        </View>
      );
    }

    return (
      <View>
        <View>
          <View>
            <View>
              <Text>Buy monthly subscription</Text>
            </View>

            <View>
              <TouchableOpacity onPress={() => this.requestSubscription(products[0].productId)}>
                <Text>Buy</Text>
              </TouchableOpacity>
            </View>
          </View>
        </View>
      </View>
    );
  }
}

[mzablockifm]

I upgraded React Native to 0.63.2 but it haven't helped.

[mzablockifm]

After bumping react-native-iap to 4.6.3 no change.

[mwerder]

I have exactly the same issue, used to be on 4.4.9, bumped to 4.6.3 and still occurs
Were you able to fix it or did you figure out a workaround?

[mzablockifm]

Unfortunately I don't have solution for this.

[hyochan]

This is very strange. Are you saying that you attempt to purchase again after the first purchase, the purchaseUpdatedListener is not firing? I've tested this earlier and it should keep firing until you kill the listener.

[hyochan]

Oh, I see. You are having a problem with the next subscription event. Let me test this out and come back.

[mj-iosdev]

We are facing the same issue, I was using 4.4.9 and tried to downgrade and upgrade to latest 5.1.1 but result is still same. Only getting event first time.

[Kalesberg]

any solution to this?

[mzablockifm]

As a temporary solution I save first receipt from subscription event and validate it on each application initialization - it works, but I tested it only for Android.

[Kalesberg]

Hi, @hyochan
Any idea when this will be resolved?

thanks

[hyochan]

Thanks for the reminder! I'll test this out tomorrow.

[Kalesberg]

@hyochan
I know you are still working on the issue, just wanted to know about the next patch date for this issue as our entire team is waiting for this one.
Thank you

[hyochan]

@Kalesberg I will definitely try out this week and share updates. However, this library is used by many others and the implementation on purchaseUpdatedListner hasn't been changed since then. I might have to make a reproducible example firstly. I'll try this week.

[hyochan]

Related for iOS in #1160

[Kalesberg]

@hyochan
Appreciate it!!

[hyochan]

@Kalesberg Could you kindly verify that android.test.purchased also fires multiple times?

[Kalesberg]

@hyochan will do that!

[Kalesberg]

@hyochan
Our product is only for subscription base, so android.test.purchased cannot best testified.
So I tried to use your demo app in this library and added test.sub1 but I was not able to get any product with it

[hyochan]

@Kalesberg Could you put android logcat where it triggers purchaseUpdatedListener?

• https://github.com/dooboolab/react-native-iap/blob/07f0354d5b0a06d06b84b1b3f0186955e1f6adc8/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L569?

Please tell me what's coming in billingResult and purchases.

[Kalesberg]

@hyochan , hope it helps
really looking forward to this patch release

[hyochan]

I am trying to look into this now. By the way can you give me better file format? rtf file is hard to open in my env which is chromeos. You may also send me an email (hyo@dooboolab.com) if you think it has privacy issue.

[hyochan]

@Kalesberg You may also check this one out. https://stackoverflow.com/questions/56744971/google-play-billing-library-developer-error-code-5-if-i-want-to-consume-or-ackno

[Kalesberg]

@hyochan
Does this mean there is nothing wrong with this plugin?

[Kalesberg]

the iOS version works fine but just the android phones are problematic

[hyochan]

We are just finding out the problem. However, following the logcat you've provided, it looks like to me that the acknowledgePurchase which is finishTransaction didn't work properly since the purchase was on the air. I've shared the stackoverflow which also talks about the similar situation.

[Kalesberg]

@hyochan
the problem persists even in test subscription mode which should always succeed

[Kalesberg]

@hyochan , any updates on the plugin?

[mzablockifm]

Current state (with newest version of iap) for ios: app receives first receipt and then when staying in foreground it won't receive next receipt. After closing app and opening it again it gets all pending receipts.

[nishanttatva]

@hyochan
For android, the purchaseUpdatedListener is called for first time when subscription is bought, and it is verified successfully by my backend server. But the auto-renewal events are not getting received in the app. I tried keeping in foreground, background and also kill and relaunch app. Still purchaseUpdatedListener is not called.

[nishanttatva]

Could you put android logcat where it triggers purchaseUpdatedListener?

• https://github.com/dooboolab/react-native-iap/blob/07f0354d5b0a06d06b84b1b3f0186955e1f6adc8/android/src/main/java/com/dooboolab/RNIap/RNIapModule.java#L569

Please tell me what's coming in billingResult and purchases.

@hyochan added the logs, the purchase listener is called with, but purchases size is 0

[kesha-antonov]

Hi guys,
did you solve this?

[andresesfm]

Hello, can somebody check if this is still an issue in 6.1.0 or newer? I have the feeling this was caused by a race condition in these two statements: c44e0fc#diff-00c325bb857787738381a0cfd47136178fec851cdd5c2c300346067214e62678R128-R132 (just a hunch)

[pafry7]

We end up using Real-time developer notifications for handling renewals and cancellations. I think that many people that are coming from web background, assume that every renewal will trigger the listener.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

[herbertvuijk]

Having this issue still in 2022. Unfortunately I dont see any thing in this thread that explains what is happening. On IOS its working fine and I'm receiving the purchase updates, on Android I only receive the first receipt and then the monthly renewal receipts never arrives to IAP.purchaseUpdatedListener

[andresesfm]

on iOS you get the renewal updates on the client.
on Android, your backaned subscribes to changes (server to server updates)

[herbertvuijk]

Ok, thanks that explains a lot. Will look into the server 2 server part.