Anyone having trouble with In-App purchase not activating in app?

Question

Created Jun ’20

Replies 3

Boosts 0

Participants 4

I have many users complaining they purchase our consumable In-App purchase on out iOS app but it does not work. they are billed so the payment has gone through but the function in the app that is suppose to be enabled does not enable, I then tell the user to try it again and the second time they purchase this it works and the features are then enabled. The user then needs to reach out to Apple for a refund of the duplicate purchase.

I am not a programmer but have had many programmers look at this and there seems to be no issue with the app so I am thinking this is an issue on Apples end. Wondering if anyone else has had similar experience?

Boost

Answer 1

junkpile OP

Jun ’20

Is it possible this is the so-called “StoreKit flow” where the user is directed to the App Store app to update an expired credit card for example? In that situation, your transaction observer will receive two callbacks - the first failed, and the second success. Your code needs to be able to handle that case. Unfortunately I’m not aware of any way to simulate it to test said code. 😕

0

Answer 2

akiladilsh OP

Jun ’20

I recently implemented consumable feature in one of my app. So what I did was I made a api call to our backend upon succession on in app purchase and it didn't cause any issue in application or in submission try this if your willing to go for it

0

Answer 3

OP

Apple

Jun ’20

If this is an Apple problem, I'd submit a bug report using the Apple Developer Feedback Assistant web page. It will help to include diagnostic information as evidence that the problem lies with Apple. If you can replicate the issue, then I'd install the StoreKit Profile as is available on the Bug Reporting Profiles and Log page <https://developer.apple.com/bug-reporting/profiles-and-logs/> and capture a console log from the device and include it with the bug report <https://feedbackassistant.apple.com>. However, it's not clear to me that this is an Apple issue -

When a user attempts an in-app purchase and the StoreKit UI indicates that the transaction was successful, one can assume that the application's updatedTransactions delegate method is called with the .purchased transactionState. At this point, it's the responsibility of the app to handle the successful transaction indication. This raises the question - what does the app do to process the .purchased transactionState. What might cause the application to fail to provide the services associated with the in-app purchase?

Does the application log the failure condition to the device console log? My guess is that you are unable to replicate this issue. If the problem is only happening to your customers, then the issue requires that you obtain diagnostic logging from the affected user.

If the app's updatedTransaction delegate is being called with the .purchased transactionState and the app detects an issue, make sure that the app does not call finishTransaction. The finishTransaction call should only be made after the app has provided the paid for content to the customer. As a reminder, you should also make sure that the app calls addTransactionObserver at app launch time. If the finishTransaction call is not used, the transaction remains on the app queue and will be detected when the transactionObserver queries the App Store for queued transactions.

rich kubota - rkubota@apple.com
developer technical support CoreOS/Hardware/MFI

0