buySubscription returns E_UNKNOWN despite successful purchase #287

Gaia-Nutrition · 2018-10-13T15:39:54Z

Version of react-native-iap

2.2.2 (because any newer version fails on iOS due to #279)

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

iOS

Expected behavior

No error should be thrown. Purchase was successful (live and in production)

Actual behavior

E_UNKNOWN error is returned from Promise
Our Sentry.io error tracking reports this:

{"framesToPop":1,"code":"E_UNKNOWN","nativeStackIOS":["0   LuCoaching                          0x000000010062f6fc LuCoaching + 1996540","1   LuCoaching                          0x000000010060aa98 LuCoaching + 1845912","2   LuCoaching                          0x00000001007cad98 __cxa_throw + 438380","3   LuCoaching                          0x00000001007cc62c __cxa_throw + 444672","4   libdispatch.dylib                   0x000000019d078484 <redacted> + 16","5   libdispatch.dylib                   0x000000019d025610 <redacted> + 56","6   LuCoaching                          0x00000001007cc46c __cxa_throw + 444224","7   libdispatch.dylib                   0x000000019d0776c8 <redacted> + 24","8   libdispatch.dylib                   0x000000019d078484 <redacted> + 16","9   libdispatch.dylib                   0x000000019d0249ec <redacted> + 1068","10  CoreFoundation                      0x000000019d5ce1bc <redacted> + 12","11  CoreFoundation                      0x000000019d5c9084 <redacted> + 1964","12  CoreFoundation                      0x000000019d5c85b8 CFRunLoopRunSpecific + 436","13  GraphicsServices                    0x000000019f83c584 GSEventRunModal + 100","14  UIKitCore                           0x00000001ca444bc8 UIApplicationMain + 212","15  LuCoaching                          0x000000010044d110 LuCoaching + 20752","16  libdyld.dylib                       0x000000019d088b94 <redacted> + 4"],"userInfo":{"NSLocalizedDescription":"Verbindung mit iTunes Store nicht möglich"},"domain":"SKErrorDomain","line":26,"column":1877,"sourceURL":"/var/containers/Bundle/Application/818C8439-E250-42E8-AD57-EC4FB5FE5547/LuCoaching.app/main.jsbundle"}

Tested environment (Emulator? Real Device?)

Real Device. Live customers. Very consistenlty fails

Steps to reproduce the behavior

When testing the procedure with Sandbox users the error cannot be reproduced.

The text was updated successfully, but these errors were encountered:

JJMoon · 2018-10-15T02:55:05Z

@Gaia-Nutrition Would you check this old-issue? It' might be same cause.
#201

Gaia-Nutrition · 2018-10-15T07:31:25Z

@JJMoon in #201 the error was E_DEVELOPER_ERROR and was caused by not populating the validProducts list using getSubscriptions().
However, I am calling the function before trying to perform the checkout and I also get a different error.
But now that I think about it. It could happen that there is quite some time delay between the getSubscriptions() and buySubscription() call caused by the user reconsidering if he/she wants to perform the purchase. Could this be an issue? The app might have been backgrounded in the meantime.
EDIT: But then again the purchase is executed successfully so the issue must be where the app store response is being processed

Jerome91410 · 2018-10-16T13:58:19Z

Hello,

Same issue behavior with "buyProductWithoutFinishTransaction" or "buyProduct".

Version 2.2.1

the return stored is
{ "framesToPop": 1, "code": "E_UNKNOWN", "nativeStackIOS": [...], "userInfo": { "NSLocalizedDescription": "Connexion à l’iTunes Store impossible" }, "domain": "SKErrorDomain", "line": 16, "column": 1599, "sourceURL": "..." }

We updated the module because we reproduce this bug on production with previous versions .

fierysolid · 2018-10-16T19:39:18Z

The interesting part is that the restore purchase also fails for my users when this happens. It only happens to about 1% of our iOS users.

Jerome91410 · 2018-10-16T22:12:14Z

@fierysolid Same case , we are around 5% of purchases on iOS who failed. When the customer try to buy again, he has a restore purchase pop up.

hyochan · 2018-10-24T21:08:54Z

Hi everyone. I hope it is fixed in our new version today which is 2.3.15. I've have noticed that using NSDictionaryin ios purely is not safe to use and may cause unexpected behavior. I've fixed this and hope now it works ok in every device. Please test this out.

hyochan · 2018-10-24T23:31:10Z

Please reopen when still facing the problem.

danrevah · 2018-10-26T14:02:02Z

@dooboolab
I still get this issue while using buySubscription() with a sandbox tester user with iPhone 6S.

{"userInfo":{"NSLocalizedDescription":"Cannot connect to iTunes Store"}}

hyochan · 2018-10-26T17:13:44Z

@danrevah So you've tried our new version which is 2.3.15? @JJMoon Can you please test this one more time?

danrevah · 2018-10-26T20:34:23Z

@dooboolab yes Im using that version.

hyochan · 2018-10-26T22:21:22Z

@danrevah Please try 2.3.16.

danrevah · 2018-10-27T12:24:47Z

@dooboolab it worked once, but while I tried again I kept getting this errors. (used v 2.3.17)

hyochan · 2018-10-27T12:32:49Z

@JJMoon Do you have any clue on this? he is using iPhone6S

hyochan · 2018-10-28T04:44:40Z

I've reopened the issue. cc @JJMoon

If more people votes to this issue, we will try harder to dig this more deeply.

JJMoon · 2018-10-28T08:31:48Z

@danrevah I hope you to refer to this document.
https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/StoreKitGuide/Chapters/Subscriptions.html#//apple_ref/doc/uid/TP40008267-CH7-SW6
To test subscription in sandbox mode, you need to re-purchase subscription after some time.
And you might need to cancel it to purchase again.
And there are some weird reactions from Apple sandbox server, which makes the test more difficult.

hyochan · 2018-10-28T11:05:30Z

If @JJMoon case is the problem we may close this again. Please reopen if you still needs help on this one. @danrevah

yasirsalim22 · 2018-12-13T13:07:25Z

@JJMoon I have faced the same issue. any solution? buySubscription throws exception and yet payment is deducted. I need to have results data to store and validate them.
@hyochans

cbfranca · 2019-02-07T14:38:44Z

+1 I've the same problem

hyochan · 2019-02-07T16:31:01Z

Try using addAdditionalSuccessPurchaseListenerIOS in buySubscription also. This is same issue as in #307.

cbfranca · 2019-02-08T20:45:44Z

Try using addAdditionalSuccessPurchaseListenerIOS in buySubscription also. This is same issue as in #307.

Has someone already using in production ?

cbfranca · 2019-02-11T13:21:22Z

@hyochan , I've tried to do that but without success.

if (subscription && subscription.success) {
      this.props.subscribe(subscription.result);
    } else {
      if (Platform.OS === 'ios') {
        const sub = RNIap.addAdditionalSuccessPurchaseListenerIOS(async (purchase) => {
          this.props.subscribe(purchase); // -> This code is never fired
          sub.remove();
        });
      }
    }

hyochan · 2019-02-11T13:57:03Z

@cbfranca Please follow the actual code. You are not even using promises. You should listen to addAdditionalSuccessPurchaseListenerIOS after the promise rejection.

Also you do not need extra Platform.OS === 'ios'.

cbfranca · 2019-02-11T17:19:57Z

@hyochan
Sorry for my ignorance, but I do not think I understood correctly. I followed the same bases of the example, suiting my scenario. I created an abstraction that treats this promise using async / await. This subscription object is returned by my abstraction.

static purchaseSubscription(newSubscriptionID, currentSubscriptionID) {
    if (Platform.OS === 'ios') {
      const purchaseResult = KinvoBilling.purchaseSubscriptionIOS(newSubscriptionID);
      return purchaseResult;
    }

    const purchaseResult = KinvoBilling.purchaseSubscriptionANDROID(newSubscriptionID, currentSubscriptionID);
    return purchaseResult;
  }

  static purchaseSubscriptionANDROID = async (newSubscriptionID, currentSubscriptionID) => {
    const hasCurrentSubscription = currentSubscriptionID !== null;

    if (hasCurrentSubscription) {
      const purchaseResult = KinvoBilling.updateSubscription(newSubscriptionID, currentSubscriptionID);
      return purchaseResult;
    }
    const purchaseResult = KinvoBilling.buySubscription(newSubscriptionID);
    return purchaseResult;
  }

  static purchaseSubscriptionIOS = async (subscriptionID) => {
    await KinvoBilling.getSubscriptions();
    const purchaseResult = await KinvoBilling.buySubscription(subscriptionID);

    return purchaseResult;
}

hyochan · 2019-02-12T05:41:09Z

@cbfranca

static purchaseSubscriptionIOS = async (subscriptionID) => {
    await KinvoBilling.getSubscriptions();
    try {
      const purchaseResult = await KinvoBilling.buySubscription(subscriptionID);
    } catch (err) {
     const subscription = RNIap.addAdditionalSuccessPurchaseListenerIOS(async (purchase) => {
        // dooboolab => check the call here.
        this.setState({ receipt: purchase.transactionReceipt }, () => this.goToNext());
        subscription.remove();
     }
    }
    return purchaseResult;
}

Check above code. I think you need to refactor your code to fit its lifecycle.

cbfranca · 2019-02-12T11:40:51Z

@hyochan Not works for me.

My test cenario is:

Purchase the monthly subscription plan - Ok
Upgrade to annual subscription plan - Fails and listener not working

Another doubt: Do I have to use finishTransaction() in subscriptions too ?

gerbus · 2019-03-17T21:53:42Z

I'm seeing this error too. And I think I know one way to reproduce it.

Version of react-native-iap

^2.4.1

Version of react-native

https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz

Platform

iOS, when testing in TestFlight on a real device.

Observations

I noticed that when any RNIap functions were called in my app, iOS would ask me to enter a password for a previous iTunes/App Store user (which I have since logged out and replaced via iOS Settings). I read somewhere online that this is an issue that dogs iPhone users from time to time: sometimes an app is bought with one iTunes account, then the phone is switched to a new iTunes account, but the app continues to ask for the password for the old iTunes account.

I tried to delete my app (and TestFlight) and reinstall with the new App Store user, to no avail. The only way I could get rid of this behavior was to wipe the device. Once I did this, I could no longer reproduce this error.

Actual Behavior

buySubscription()
Select Continue when presented with iOS modal "Subscription Terms"
Select OK when presented with iOS modal "Confirm Subscription"
Error thrown by buySubscription():

{
   code: E_UNKNOWN, 
   column: 1565, 
   domain: NSURLErrorDomain, 
   framesToPop: 1, 
   line: 20, 
   nativeStackIOS: [...],
   sourceURL: ...,
   userInfo: {
      _kCFStreamErrorCodeKey: -4, 
      _kCFStreamErrorDomainKey: 4, 
      NSErrorFailingURLKey: None, 
      NSErrorFailingURLStringKey: https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, 
      NSLocalizedDescription: Cannot connect to iTunes Store, 
      NSUnderlyingError: {
         code: "-1005", 
         domain: "kCFErrorDomainCFNetwork", 
         message: "underlying error", 
         nativeStackIOS: [...],
         userInfo:{"NSErrorPeerAddressKey":null,"_kCFStreamErrorCodeKey":-4,"_kCFStreamErrorDomainKey":4}
      }
   }
}

Steps to reproduce the behavior

Create a test user in App Store Connect
Install app from App Store (or invite test user to TestFlight and install TestFlight and then app through TestFlight)
Purchase a subscription in app
Let the subscription expire
Logout iOS Apple ID (Settings > Apple ID, Sign Out)
Login new Apple ID
Purchase a subscription in app

Hope this helps someone!

cbfranca · 2019-04-23T16:15:52Z

@hyochan

After trying many things I'm still with the same problem and more. At code bellow, the RNIap.buySubscription(sku) returns undefined. Please, did someone solve it?

static purchaseSubscriptionIOS = async (subscriptionID) => {
  await KinvoBilling.getSubscriptions();

  try {
    const purchaseResult = await RNIap.buySubscription(subscriptionID);
    return createResponse(true, purchaseResult);
  } catch (error) {
    const subscription = RNIap.addAdditionalSuccessPurchaseListenerIOS(async (purchase) => {
      // dooboolab => check the call here.
      console.tron.log('--- ERROR ----');
      console.tron.log(error);
      console.tron.log('--- PURCHASE ----');
      console.tron.log(purchase);
      const result = purchase;
      subscription.remove();
      console.tron.log(result);

      if (result) {
        return createResponse(true, result);
      }
      return createResponse(false, result);
    });
  }
};

dphaener · 2019-09-09T13:33:56Z

👍 We are experiencing this issue was well. It seems to be happening to about 10% of our users currently. We're going to try adding this listener, but I don't think that ultimately this is a great solution. @hyochan Is there any way we can get more detailed information in the cases where this throws, or is that a standard response from the StoreKit APIs? In every error case the message seems to be "Cannot connect to iTunes Store", even when the purchase is successful.

drbarto · 2019-09-14T14:33:51Z

We have a very similar problem with 3.4.6: 1st purchase attempt fails with E_UNKOWN, retrying succeeds. However, for us this happens with buyProduct, not with buySubscription. @hyochan could this still be the same root cause?

agusvazquez · 2019-11-15T23:02:01Z

Hello! I'm experiencing the same issue after calling RNIap.requestSubscription() I get an undefined result but the payment succeeds, the credit card is charged.

The only way of that user to get it past is by restoring the purchase.

Did anyone got a fix for this? I'm using version 3.5.9

JJMoon added 📱 iOS Related to iOS 🐛 bug Something isn't working labels Oct 14, 2018

eis mentioned this issue Oct 17, 2018

restoring purchase made with redeem code doesn't work on IPhone SE, works on others #288

Closed

hyochan closed this as completed Oct 24, 2018

hyochan reopened this Oct 28, 2018

hyochan closed this as completed Oct 28, 2018

lc3t35 mentioned this issue Nov 27, 2018

RNIap.buySubscription error : E_DEVELOPER_ERROR #328

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

buySubscription returns E_UNKNOWN despite successful purchase #287

buySubscription returns E_UNKNOWN despite successful purchase #287

Gaia-Nutrition commented Oct 13, 2018

JJMoon commented Oct 15, 2018

Gaia-Nutrition commented Oct 15, 2018 •

edited

Jerome91410 commented Oct 16, 2018

fierysolid commented Oct 16, 2018 •

edited

Jerome91410 commented Oct 16, 2018

hyochan commented Oct 24, 2018 •

edited

hyochan commented Oct 24, 2018

danrevah commented Oct 26, 2018 •

edited

hyochan commented Oct 26, 2018

danrevah commented Oct 26, 2018

hyochan commented Oct 26, 2018

danrevah commented Oct 27, 2018 •

edited

hyochan commented Oct 27, 2018

hyochan commented Oct 28, 2018

JJMoon commented Oct 28, 2018

hyochan commented Oct 28, 2018

yasirsalim22 commented Dec 13, 2018 •

edited

cbfranca commented Feb 7, 2019

hyochan commented Feb 7, 2019

cbfranca commented Feb 8, 2019 •

edited

cbfranca commented Feb 11, 2019 •

edited

hyochan commented Feb 11, 2019

cbfranca commented Feb 11, 2019 •

edited

hyochan commented Feb 12, 2019 •

edited

cbfranca commented Feb 12, 2019

gerbus commented Mar 17, 2019 •

edited

cbfranca commented Apr 23, 2019 •

edited

dphaener commented Sep 9, 2019

drbarto commented Sep 14, 2019

agusvazquez commented Nov 15, 2019 •

edited

buySubscription returns E_UNKNOWN despite successful purchase #287

buySubscription returns E_UNKNOWN despite successful purchase #287

Comments

Gaia-Nutrition commented Oct 13, 2018

Version of react-native-iap

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

Expected behavior

Actual behavior

Tested environment (Emulator? Real Device?)

Steps to reproduce the behavior

JJMoon commented Oct 15, 2018

Gaia-Nutrition commented Oct 15, 2018 • edited

Jerome91410 commented Oct 16, 2018

fierysolid commented Oct 16, 2018 • edited

Jerome91410 commented Oct 16, 2018

hyochan commented Oct 24, 2018 • edited

hyochan commented Oct 24, 2018

danrevah commented Oct 26, 2018 • edited

hyochan commented Oct 26, 2018

danrevah commented Oct 26, 2018

hyochan commented Oct 26, 2018

danrevah commented Oct 27, 2018 • edited

hyochan commented Oct 27, 2018

hyochan commented Oct 28, 2018

JJMoon commented Oct 28, 2018

hyochan commented Oct 28, 2018

yasirsalim22 commented Dec 13, 2018 • edited

cbfranca commented Feb 7, 2019

hyochan commented Feb 7, 2019

cbfranca commented Feb 8, 2019 • edited

cbfranca commented Feb 11, 2019 • edited

hyochan commented Feb 11, 2019

cbfranca commented Feb 11, 2019 • edited

hyochan commented Feb 12, 2019 • edited

cbfranca commented Feb 12, 2019

gerbus commented Mar 17, 2019 • edited

Version of react-native-iap

Version of react-native

Platform

Observations

Actual Behavior

Steps to reproduce the behavior

cbfranca commented Apr 23, 2019 • edited

dphaener commented Sep 9, 2019

drbarto commented Sep 14, 2019

agusvazquez commented Nov 15, 2019 • edited

Gaia-Nutrition commented Oct 15, 2018 •

edited

fierysolid commented Oct 16, 2018 •

edited

hyochan commented Oct 24, 2018 •

edited

danrevah commented Oct 26, 2018 •

edited

danrevah commented Oct 27, 2018 •

edited

yasirsalim22 commented Dec 13, 2018 •

edited

cbfranca commented Feb 8, 2019 •

edited

cbfranca commented Feb 11, 2019 •

edited

cbfranca commented Feb 11, 2019 •

edited

hyochan commented Feb 12, 2019 •

edited

gerbus commented Mar 17, 2019 •

edited

cbfranca commented Apr 23, 2019 •

edited

agusvazquez commented Nov 15, 2019 •

edited