Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purchase Flow succeeds and then restarts on FIRST purchase with new sandbox account. #597

Closed
louiskabo opened this issue Nov 20, 2020 · 17 comments

Comments

@louiskabo
Copy link

Bug Report

While testing some new features, I came across this bug and am able to reproduce it. It appears that when you make a first purchase in sandbox, you get the all clear from the apple side of the transaction, then the purchase confirmation window starts again and you have to go through the motions to select purchase a seconds time. This only happens on the very first purchase you make with a new sandbox account. Subsequent purchases and renewals do not cause such action.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new sandbox account
  2. uninstall and reinstall your app from your computer so as to delete all old data
  3. attempt to make any In-App purchase

Expected behavior
You should go through the billing flow once, the purchase should complete and the product be made available. Yet this is not happening. As stated, on this first purchase, you are made to basically "start over" with the whole billing flow procedure like it hadn't;t happened before.

Platform Information

  • OS: iOS 14.2 Xcode 12.2
  • Purchase Type: Testes with non-consumables and Auto-Renewing Subscriptions
  • Environment: Sandbox

Thank you.

@jjkaufman
Copy link

@louiskabo did you find a workaround? I'm seeing this too

@louiskabo
Copy link
Author

I did not, and I am unable to confirm if it is the same in live with a new iCloud account...

@RockXeng
Copy link

RockXeng commented Dec 5, 2020

I'm seeing this too, How to solve it?

@RockXeng
Copy link

RockXeng commented Dec 6, 2020

@louiskabo did you find a workaround?

@louiskabo
Copy link
Author

Unfortunately no, I did not. But I have submitted several updates since discovery and no issues have been raised by review.

I’d be interested to know if this happens live with a new iCloud account..

If u find the glitch, please update this post.

@RockXeng
Copy link

RockXeng commented Dec 6, 2020

@louiskabo Because of this problem, I was rejected by Apple several times, so I was confused how to solve it.

@louiskabo
Copy link
Author

Are you sure it was because of this particular bug? There was another bug that made the test user continue to provide login credentials. Are you sure it is not that bug?

@louiskabo
Copy link
Author

@RockXeng check out #397

Make sure this isn’t why your getting rejected. What was the specific rejection message they sent you?

@RockXeng
Copy link

RockXeng commented Dec 6, 2020

@louiskabo We found that your in-app purchase products exhibited one or more bugs when reviewed on iPad running iOS 14.2 on Wi-Fi.

Specifically, the In-App Purchase (IAP) results in an error.

Below are the steps to reproduce the issue:

  1. Launch the application
  2. Navigate 开通会员 page
  3. Proceed to purchase one of the IAP products
  4. IAP confirmation window appears
  5. Confirm Purchase
  6. User is prompted with Purchase Successful message
  7. IAP confirmation window appears again

@RockXeng
Copy link

RockXeng commented Dec 6, 2020

I'm sure this isn’t #397 reject reason.

@louiskabo
Copy link
Author

Interesting. I have not found the work around For this but if your getting rejected because of it, I’d say we need to.. if you figure it out, please update this post, I’ll do the same.

@RockXeng
Copy link

RockXeng commented Dec 6, 2020

I just implemented the IAP function by myself, and I will also pop up the confirmation popup twice. I think this should be a bug in the iOS system.

let payment = SKPayment(product: skProduct)
SKPaymentQueue.default().add(self)
SKPaymentQueue.default().add(payment)

@louiskabo
Copy link
Author

Excellent. I think we can close this report then. You should document your findings, report them to Apple and appeal your rejection.

Thank you

@louiskabo
Copy link
Author

@RockXeng, any luck? Please post your Apple bug report # here for others to reference. if they have similar rejections.

Btw 呢 说 汉语吗?我是数中文额生。我是不很好。 lol

@louiskabo
Copy link
Author

I can also confirm this has nothing to do with swifty store kit and is an apple bug..

@KKKoTTT
Copy link

KKKoTTT commented Feb 16, 2021

@louiskabo I am having the same issue. For me it happens when I'm using the release build configuration, but everything works good in the debug one. I'm not sure if this will work in the published app, could you please share how you eventually solved this problem?

@louiskabo
Copy link
Author

as long as what you are experiencing is this specific bug:

This is an apple bug and does not have anything to do with swifty. I confirmed this by testing in another app that does not use swifty, but uses a simple consumable product IAP with plain StoreKit and the same thing happened.

I have submitted a few updates to Apple since this and have not had issues with review. It seems that it does not happen in production.

You could submit a bug report and then save that bug report number for repeal if your app gets rejected, would be my advice.

To further verify, try just making a purchase using StoreKit to see if this bug still exists and is your problem, otherwise start a new bug report here as this question is closed/resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants