nfc v5.6.0

Author: marchbold

docs/inappbilling/_includes/add-manual.mdx

@@ -61,4 +61,6 @@ This ANE requires the following Google Play Services:
 You must include the above native extensions in your application along with this extension,
 and you need to ensure they are packaged with your application.
 
-You can access the Google Play Services client library extensions here: [https://github.com/distriqt/ANE-GooglePlayServices](https://github.com/distriqt/ANE-GooglePlayServices).
+You can access the repositories for these client library extensions here: 
+- [Google Play Services](https://github.com/distriqt/ANE-GooglePlayServices).
+- [Google Play](https://github.com/airnativeextensions/ANE-GooglePlay)

docs/inappbilling/add-the-extension.mdx

@@ -1,6 +1,6 @@
 ---
 title: Add the Extension
-sidebar_label: Add the Extension
+sidebar_label: AIR
 ---
 
 import Tabs from '@theme/Tabs'
@@ -48,14 +48,12 @@ However you can choose to install it manually, as you would have done in the pas
     {label: 'APM', value: 'apm'},
     {label: 'Manual', value: 'manual'},
   ]}>
-
-  <TabItem value="apm" >
+<TabItem value="apm" >
 	<InstallAPM/>
-  </TabItem>
-  <TabItem value="manual" >
+</TabItem>
+<TabItem value="manual" >
 	<InstallManual/>
-  </TabItem>
-  
+</TabItem>
 </Tabs>
 
 
@@ -69,13 +67,12 @@ However you can choose to install it manually, as you would have done in the pas
     {label: 'Manual', value: 'manual'},
   ]}>
 
-  <TabItem value="apm" >
+<TabItem value="apm" >
 	<AppDescriptorAPM/>
-  </TabItem>
-  <TabItem value="manual" >
+</TabItem>
+<TabItem value="manual" >
 	<AppDescriptorManual/>
-  </TabItem>
-  
+</TabItem>
 </Tabs>
 
 

docs/inappbilling/add-the-plugin.md

@@ -0,0 +1,63 @@
+---
+title: Add the Plugin
+sidebar_label: Unity
+---
+
+First step is always to add the plugin to your development environment. 
+
+
+## Asset Store
+
+Open the Asset Store in your browser and add the plugin to your assets.
+
+Open the Package Manager (Window > Package Manager) in the Unity Editor and select the "My Assets" section. Select the plugin, and click Import.
+
+
+## Manual Installation
+
+In unity you import the package by selecting `Assets / Import Package / Custom Package ...` and then browsing to the unity plugin package file: `com.distriqt.InAppBilling.unitypackage`.
+
+![](images/unity-import-package.png)
+
+You can manually download the extension from our repository:
+
+- https://github.com/distriqt/ANE-InAppBilling
+
+
+
+## Import the Plugin
+
+
+This will present the import dialog and display all the files for the plugin, make sure all the files are selected.
+
+The plugin will be added to your project and you can now use the plugins functionality in your application.
+
+
+:::note Proguard
+If you are using a custom proguard configuration you may need to add the following line to ensure the interface class for the plugin is accessible to unity at runtime.
+
+```
+-keep class com.distriqt.extension.inappbilling.InAppBillingUnityPlugin {*;}
+```
+:::
+
+
+
+## Checking for Support
+
+You can use the `isSupported` flag to determine if this extension is supported on the current platform and device.
+
+This allows you to react to whether the functionality is available on the device and provide an alternative solution if not.
+
+
+```csharp
+if (InAppBilling.isSupported)
+{
+	// Functionality here
+}
+```
+
+
+
+
+

docs/inappbilling/application-receipt.md

@@ -24,7 +24,7 @@ It is up to you to decide if this is required for your situation.
 
 
 :::info
-The "Application Receipt" variant performs local validation of the application receipt to retrieve purchase information and makes this information available through the [Get Purchases](get-purchases.md) API.
+The "Application Receipt" variant performs local validation of the application receipt to retrieve purchase information and makes this information available through the [Get Purchases](get-purchases) API.
 :::
 
 

docs/inappbilling/billing-service.md docs/inappbilling/billing-service.mdxdocs/inappbilling/billing-service.md renamed to docs/inappbilling/billing-service.mdx

@@ -3,6 +3,9 @@ title: Setup Billing Service
 sidebar_label: Setup Billing Service
 ---
 
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
 ## Billing Service
 
 Before starting here you should make sure you have already setup the service for your application 
@@ -43,17 +46,21 @@ sure that you handle the event appropriately.
 
 ## Events
 
+<Tabs groupId="framework" defaultValue="air" values={[
+    {label: 'AIR', value: 'air'},
+    {label: 'Unity', value: 'unity'},
+  ]}>
+  <TabItem value="air" >
+  
 We suggest you listen to the following four events before calling setup:
 
 - `InAppBillingEvent.SETUP_SUCCESS`: Dispatched when setup is successfully completed;
 - `InAppBillingEvent.SETUP_FAILURE`: Dispatched when there was an error during setup;
 - `PurchaseEvent.PURCHASES_UPDATED`: Dispatched if there are pending purchases needing to be processed;
-- `PurchaseRequestEvent.SHOULD_ADD_PURCHASE`: Dispatched if the app was launched from an AppStore promotional purchase (see [Promotions](promotions.md)).
+- `PurchaseRequestEvent.SHOULD_ADD_PURCHASE`: Dispatched if the app was launched from an AppStore promotional purchase (see [Promotions](promotions)).
 
 
 ```actionscript
-InAppBilling.service.addEventListener( InAppBillingEvent.SETUP_SUCCESS, setup_successHandler );
-InAppBilling.service.addEventListener( InAppBillingEvent.SETUP_FAILURE, setup_failureHandler );
 InAppBilling.service.addEventListener( PurchaseEvent.PURCHASES_UPDATED, purchases_updatedHandler );
 InAppBilling.service.addEventListener( PurchaseRequestEvent.SHOULD_ADD_PURCHASE, purchaseRequest_shouldAddPurchaseHandler );
 						
@@ -63,12 +70,38 @@ InAppBilling.service.setup(
 );
 ```
 
+  </TabItem>
+  <TabItem value="unity" >
+
+We suggest you listen to the following four events before calling setup:
+
+- `InAppBilling.Instance.Events.OnPurchasesUpdated`: Dispatched if there are pending purchases needing to be processed;
+- `InAppBilling.Instance.Events.OnShouldAddPurchase`: Dispatched if the app was launched from an AppStore promotional purchase (see [Promotions](promotions));
+
+```csharp
+InAppBilling.Instance.Events.OnPurchasesUpdated += OnPurchasesUpdated;
+InAppBilling.Instance.Events.OnShouldAddPurchase += OnShouldAddPurchase;
+
+InAppBilling.Instance.Setup(
+        new BillingService()
+            .SetGooglePlayPublicKey( GOOGLE_PLAY_INAPP_BILLING_KEY )
+);                
+```
+
+  </TabItem>
+</Tabs>
 
 
 ## Service Type
 
 The billing service type will be automatically selected based on the default of the current device platform. However we suggest you specify the service type in your `BillingService` using `setServiceType()` to specify a particular service:
 
+<Tabs groupId="framework" defaultValue="air" values={[
+    {label: 'AIR', value: 'air'},
+    {label: 'Unity', value: 'unity'},
+  ]}>
+  <TabItem value="air" >
+
 ```actionscript
 var service:BillingService = new BillingService(  )
     .setServiceType( InAppBillingServiceTypes.GOOGLE_PLAY_INAPP_BILLING )
@@ -77,8 +110,22 @@ var service:BillingService = new BillingService(  )
 var success:Boolean = InAppBilling.service.setup( service );
 ```
 
+  </TabItem>
+  <TabItem value="unity" >
+
+```csharp
+var service = new BillingService()
+    .SetServiceType( InAppBillingServiceTypes.GOOGLE_PLAY_INAPP_BILLING )
+    .SetGooglePlayPublicKey( GOOGLE_PLAY_INAPP_BILLING_KEY );
+InAppBilling.Instance.Setup( service );
+```
+
+  </TabItem>
+</Tabs>
+
+
 :::note 
-You do not need to call `setServiceType`. 
+You do not need to call `setServiceType()`. 
 If you do not call it then the default for the current platform will be used, 
 i.e. Apple InApp Purchases on iOS and Google's Play InApp Billing on Android.
 
@@ -93,6 +140,13 @@ Once you have completed setup it is important to check whether the user on the c
 
 For example, the latest version of Play Billing is only supported with an updated version of the Play Store app. If an older version is on the user's device the billing api will not be available.
 
+
+<Tabs groupId="framework" defaultValue="air" values={[
+    {label: 'AIR', value: 'air'},
+    {label: 'Unity', value: 'unity'},
+  ]}>
+<TabItem value="air" >
+
 To check the status call the `checkAvailability()` function and await the result. This function will dispatch an `AvailabilityEvent.COMPLETE` event or call a callback function passed as the parameter to the function.
 
 Callback:
@@ -108,7 +162,6 @@ InAppBilling.service.checkAvailability(
 
 Event:
 
-
 ```actionscript
 InAppBilling.service.addEventListener( AvailabilityEvent.COMPLETE, function( event:AvailabilityEvent ):void
 {
@@ -118,12 +171,37 @@ InAppBilling.service.checkAvailability();
 ```
 
 
+
 The `availability` value will be one of the values defined in the `InAppBillingAvailability` class:
 
+- `InAppBillingAvailability.AVAILABLE`: Service is available for products and purchases;
+- `InAppBillingAvailability.NOT_AVAILABLE`: Service is unavailable on the device;
+- `InAppBillingAvailability.STORE_UPGRADE_REQUIRED`: An update is required to the store application for this service
+
+
+
+</TabItem>
+<TabItem value="unity" >
+
+
+To check the status call the `CheckAvailability()` function and await the result. 
+
+```csharp
+InAppBilling.Instance.CheckAvailability(
+        (e) =>
+        {
+            Debug.Log( "availability = " + e.availability );
+        }
+);
+```
+The `e.availability` value will be one of the values defined in the `InAppBillingAvailability` class:
+
 - `InAppBillingAvailability.AVAILABLE`: Service is available for products and purchases;
 - `InAppBillingAvailability.NOT_AVAILABLE`: Service is unavailable on the device;
 - `InAppBillingAvailability.STORE_UPGRADE_REQUIRED`: An update is required to the store application for this service;
 
+</TabItem>
+</Tabs>
 
 You should handle the response as required and inform your users if purchasing isn't available or steps to upgrade the store application.
 
@@ -138,10 +216,24 @@ It is equally appropriate to handle those error events however we suggest an upf
 
 ## Pending Purchases
 
-Note that the pending purchases may not be available to you at the  `InAppBillingEvent.SETUP_SUCCESS` event, as they may be updated after setup has completed. This is particularly true on iOS/tvOS where the payment queue update (which populates the pending purchases) will occur a short time after setup succeeds.
+<Tabs groupId="framework" defaultValue="air" values={[
+    {label: 'AIR', value: 'air'},
+    {label: 'Unity', value: 'unity'},
+  ]}>
+<TabItem value="air" >
+
+Note that the pending purchases may not be available to you at the  `InAppBillingEvent.SETUP_SUCCESS` event, as they may be updated after setup has completed. 
+This is particularly true on iOS/tvOS where the payment queue update (which populates the pending purchases) will occur a short time after setup succeeds.
 
 This update will be indicated by a `PurchaseEvent.PURCHASES_UPDATED`, indicating there are purchases to process.
 
+</TabItem>
+<TabItem value="unity" >
 
+Note that the pending purchases may not be available to you after setup is complete, as they may be updated after this point. 
+This is particularly true on iOS/tvOS where the payment queue update (which populates the pending purchases) will occur a short time after setup succeeds.
 
+This update will be indicated by an `OnPurchasesUpdated` event, indicating there are purchases to process.
 
+</TabItem>
+</Tabs>

docs/inappbilling/catappult/catappult.md

@@ -23,7 +23,7 @@ This extension implements Catappult's Native Android Billing and not the One-Ste
 
 ## Setting up a Billing Service
 
-> The following is in addition to the documentation in [Setting up a Billing Service](../billing-service.md).
+> The following is in addition to the documentation in [Setting up a Billing Service](../billing-service).
 
 When setting up your service you will need to specify the `InAppBillingServiceTypes.CATAPPULT_NATIVE_BILLING` service type and provide your Catappult Public key. The public key is used to verify purchases to provide a level of fraud protection: