in app purchases

[Chris Sheffield]

Hi Monte,

My experience was that turning on updates and leaving them on actually caused more problems. I ended up with all kinds of weird behavior, especially when downloads did not complete. But in my case, I had large files downloading, so it was easy to interrupt them (i.e. closing the app while a download was in progress). I also didn't want the app to immediately start checking for incomplete purchases immediately when launching. It just doesn't really make sense with the way we have the app structured. So in One Minute Reader, I turn on updates when a purchase is initiated and turn them off when a purchase is finished.

Also, Apple's docs, if I remember correctly, said to wait until delivery of content is complete before sending the delivery confirmation. I know this sounds strange, but this didn't work for me. I finally tried sending the delivery confirmation as soon as purchaseStateUpdate received a "paymentReceived" state. Then, after sending delivery confirmation, the app downloads the content. I know it seems a little backwards, but again, we were getting all kinds of weird results doing it the other way when the download would get interrupted.

Anyway, not sure if this helps at all. This was just my experience, for whatever it's worth.

Chris


--
Chris Sheffield
Read Naturally, Inc.
www.readnaturally.com



On Feb 25, 2013, at 10:01 PM, Monte Goulding <monte at sweattechnologies.com> wrote:

> Howdy
> 
> A little question for those of you that have implemented in app purchases. The lesson here http://lessons.runrev.com/s/lessons/m/4069/l/48771-How-do-I-implement-in-app-purchases-in-LiveCode-
> 
> states that mobileEnablePurchaseUpdates and mobileDisablePurchaseUpdates should be turned on and off for each purchsase. However I can only assume that this purchase updates is adding and removing an SKPaymentTransactionObserver and the apple docs seem to indicate you should assign this at startup and leave it alone...
> 
> Your application should associate an observer with the payment queue when it launches, rather than wait until the user attempts to purchase an item. Transactions are not lost when an application terminates. The next time the application launches, Store Kit resumes processing transactions. Adding the observer during your application’s initialization ensures that all transactions are returned to your application.
> 
> Anyone got any comments?
> 
> Also... how interested are people in there being a desktop external for this?
> 
> Cheers
> 
> --
> M E R Goulding 
> Software development services
> Bespoke application development for vertical markets
> 
> mergExt - There's an external for that!
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode