(generated from source files using make doc-contrib)
The implementation of the unified API is a small layer built on top of the legacy "PhoneGap-InAppPurchase-iOS" plugin.
This was first decided as a temporary "get-things-done" solution. However, I found this ended-up providing a nice separation of concerns:
- the
platforms/ios-bridge.js
file exposes an API calledstorekit
that matches the iOS way of dealing with in-app purchases.- It is where the dialog with the Obj-C part happens.
- It turns that into a javascript friendly API, close to the StoreKit API.
- There are some specifities to it, so if eventually some users want to go for a platform specific implementation on iOS, they can!
- the
platforms/ios-adapter.js
connects the iOSstorekit
API with the unifiedstore
API.- It makes sure products are loaded from apple servers
- It reacts to product's changes of state, so that a product get's purchased
when
REQUESTED
, or finished whenFINISHED
for instance.
The iOS implementation monitors products changes of state to trigger
storekit
operations.
Please refer to the product life-cycle section of the documentation for better understanding of the job of this event handlers.
At first refresh, initialize the storekit API. See storekitInit()
for details.
When a product enters the store.REQUESTED state, initiate a purchase with storekit
.
When a product enters the store.FINISHED state, finish()
the storekit transaction.
storekit
doesn't provide a way to know which products have been purchases.
That is why we have to handle that ourselves, by storing the OWNED
status of a product.
Note that, until Apple provides a mean to get notified to refunds, there's no way back.
A non-consumable product, once OWNED
always will be.
This funciton will initialize the storekit API.
This initiates a chain reaction including storekitReady()
and storekitLoaded()
that will make sure products are loaded from server, set as VALID
or INVALID
, and eventually restored
to their proper OWNED
status.
It also registers the storekit
callbacks to get notified of events from the StoreKit API:
Called when storekit
has been initialized successfully.
Loads all registered products, triggers storekitLoaded()
when done.
Update the store
's product definitions when they have been loaded.
- Set the products state to
VALID
orINVALID
- Trigger the "loaded" event
- Set the products state to
OWNED
(if it is so) - Set the store status to "ready".
Note: the execution of "ready" is deferred to make sure state changes have been processed.
Called by storekit
when a purchase is in progress.
It will set the product state to INITIATED
.
Called by storekit
when a purchase have been approved.
It will set the product state to APPROVED
and associates the product
with the order's transaction identifier.
Called by storekit
when an error happens in the storekit API.
Will convert storekit errors to a store.Error
.
return true iff the product with given ID has been purchased and finished during this or a previous execution of the application.
store the boolean OWNED status of a given product.
When setup and/or load failed, the plugin will retry over and over till it can connect to the store.
However, to be nice with the battery, it'll double the retry timeout each time.
Special case, when the device goes online, it'll trigger all retry callback in the queue.