Comments on: iPhone Tutorial – In-App Purchases

By: Rob

Rob — Wed, 01 Feb 2012 08:46:00 +0000

Hi,
1. Great blog!
2. I was just wondering how I can detect when the ‘Confirm Your In App Purchase’ alert is displayed on screen?
- I tried setting up the (void)didPresentAlertView:(UIAlertView *)alertView; from UIAlertViewDelegate but that doesn’t catch the In App Purchase popup.

Any ideas?
Thanks!

By: My In-App Purchasing War Story | EJSMITHWEB

My In-App Purchasing War Story | EJSMITHWEB — Wed, 18 Jan 2012 19:03:28 +0000

[...] coming from me, that’s saying a lot.To follow a nice tutorial based on MKStorekit, go here. He gives you all the basics walk-throughs that I’m too lazy to give you. This entry was [...]

By: Inalbansal

Inalbansal — Fri, 09 Dec 2011 06:49:00 +0000

After searching through this forum and online for hours, I
can’t find an answer to the problem I’m having. Here’s the basic
scenario:

Trying to make an in-app purchase in my app in the sandbox
environment always fails. Getting the list of available products
through SKProductsRequest works fine .. I get an array of valid
SKProduct objects back. But after I queue an SKPayment in the
SKPaymentQueue, the transactionState of the SKPaymentTransaction object
that the observe gets is SKPaymentTransactionStateFailed. HOWEVER, when
I try to see WHY it failed, I find that the error property of the
SKPaymentTransaction object is nil. There is no NSError object there to
query!!

Also, in the app, no pop up ever appears to ask for the account
credentials to verify the purchase! And yes, I did first log out of my
real Apple ID in the Settings app, and I did not try to sign back in there with my test account ID. That way, there should
be a popup when I try to make a purchase asking me for my Apple ID
info, where I would enter the test account info. But that popup never
appears. The transaction just silently fails.

If I query the payment property of the failed SKPaymentTransaction
object, I find the correct SKPayment object with the correct
productIdentifier, so the failed transaction is at least asking for the
right product. So why is it failing?

Has anybody else seen this?

I’ve gone through all of the proper setup steps listed in the
documentation and elsewhere in this forum … I created a non-wildcare
app ID, activated in-app payments for that ID, created a new, dummy app
in iTunes Connect (checking “upload binary later”), created some in-app
purchase products, made them available for sale, created a new developer
provisioning profile for the new app ID, downloaded that profile and
installed it in Xcode and on my test phone, changed the bundle
identifier in the info.plist of the app, changed the code signing to use
the new provisioning profile, set up a test user in iTunes Connect with
a novel email address, etc etc etc etc etc. Like I say, I do
get an array of valid SKProduct objects from the app store servers, so
things must be set up somewhat correctly. But even after redoing
everything from scratch a few times and tweaking everything I can think
of, I can’t get a sandbox purchase to go through .. or even to get the
confirm purchase popup!

Any ideas?

By: Hokuto2035

Hokuto2035 — Mon, 05 Dec 2011 14:49:00 +0000

i have the same problem too. when i try to delete the item use “removeAllKeychainData” it returns Error says “SFHFKeychainUtilErrorDomain Code = -25300″.
Why it can not be clear?

By: James

James — Wed, 30 Nov 2011 20:56:00 +0000

We have a new app which we are going to submit to apple and it will have in app purchase.
Third party companies want to give our app away for free to their subscribers and pay us a lump sum to do so. Will apple allow us to do that and will they want any part of the lump sum we get ?
If they did allow it without requiring payment we would want to add “do you have a promo code” prior to the in app purchase and give the promo codes to the third parties. Their subscribers would then enter the promo code to get the app for free.
If it is possible – can you write the software for us ?

By: MiniMan

MiniMan — Sun, 13 Nov 2011 12:06:00 +0000

I keep getting the same problem. It’s always true when I do if([MKStoreManager isFeaturePurchased:@"com.myapp.feature"]).

Does anyone know a fix for this, please?

By: Brad

Brad — Thu, 03 Nov 2011 18:46:00 +0000

1. I wanted to test this with multiple accounts, so I deleted the app and signed out of my test user 1. I reinstalled with app but:

if([MKStoreManager isFeaturePurchased:@"com.myapp.feature"])

keeps returning true even though I would assume it shouldn’t be? I want to test the in-app process in a few different ways but can’t seem to test it after I already purchased it.

2. How do I differentiate between failed requests, and cancelled requests?

Thanks in advance for your help. After figuring out these few things, my in-app purchase headache will be complete and I would be more than happy to make a donation. Thanks.

By: guest

guest — Thu, 20 Oct 2011 11:16:00 +0000

Hi, Thank you for tutorial
Let’s say I want to make in app purchase for a magazine. Will your MKStoreKit work with newsstand on iOS5?

By: Joe Rickerby

Joe Rickerby — Tue, 04 Oct 2011 16:14:00 +0000

Just to say thank you so much for posting this tutorial, I’m sure it would have taken me a long time to get this going had I not seen this.

By: Jack

Jack — Thu, 29 Sep 2011 15:13:00 +0000

I handles this in an app I am developing for a client. If you try to repurchase from the app store apple will tell you that you already own the product and will download it again for you at no cost. Unfortunately you still may have the problem of having a buy now button that will confuse the end user. I solved this by creating a database where I stored each purchased product by product ID and user (currently UUID) but may need to change this due to apple’s plan to restrict this. When an end user goes to a buy page I check to see if the person already purchased the product and if so I change the buy button to a reload button and skip the app store entirely. This keeps the user from having to re-log into the app store. I then handle the reload from my own back-end server.