You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/inappbilling/amazon/testing.md
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,17 @@ Instead you will need to install and configure the **App Tester** application an
15
15
16
16
App Tester allows you to unit test the In-App Purchasing (IAP) functionality of your app in sandbox mode before you submit the app for publication. You download App Tester from the Amazon Appstore onto the same Android device as your app. The App Tester simulates the production environment. You run IAP-related test cases on your app, and App Tester generates API responses (that you configure using a JSON file).
17
17
18
-
19
-
The easiest way is to install the app from the Amazon Appstore
18
+
The easiest way is to install the app from the Amazon Appstore:
20
19
21
20
- On your Android mobile device, start the Amazon Appstore app.
22
21
- Search for "Amazon App Tester".
23
22
- Select the "Amazon App Tester" app. (Do not select the Web App Tester, which is a different app.)
24
23
- Tap through the prompts to download and install the app.
25
24
25
+
You can also find the application at the following link:
@@ -79,8 +82,15 @@ D/Kiwi (11971): AppstoreSDK: Production Mode: Release build or debug.amazon.s
79
82
```
80
83
81
84
82
-
:::note
83
-
You must be using a recent release of AIR, version 33.1.1.889 or higher. APK's produced in older versions of AIR are incorrectly packaged as production builds. You can work around this by using the AndroidStudioProject output if required.
85
+
86
+
:::caution Packaging Target
87
+
It is important the you use a debug build target when testing Amazon applications, ie. you must use `-target apk-debug`. This ensures AIR produces a debug build of your application that allows the Amazon AppstoreSDK to enter debug mode.
88
+
89
+
If you use a release target eg `apk-captive-runtime` then you will always see the "Production mode" warning and won't be able to test.
90
+
:::
91
+
92
+
:::note AIR Version
93
+
You must be using a recent release of AIR, version 33.1.1.889 or higher. APK's produced in older versions of AIR are always packaged as release builds. You can work around this by using the AndroidStudioProject output if required however we recommend updating the AIR SDK and using the debug target.
84
94
:::
85
95
86
96
@@ -134,15 +144,15 @@ Listener callbacks are mapped to extension events depending on the triggered cal
Copy file name to clipboardExpand all lines: docs/inappbilling/application-receipt.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The application receipt provides a record of the sale of an app and any purchase
11
11
12
12
You can use this receipt to verify purchases and check expiration of subscriptions.
13
13
14
-
There are two ways to verify a receipt’s authenticity:
14
+
There are two ways to verify a receipt's authenticity:
15
15
16
16
17
17
- On your server with the App Store. Validating receipts with the App Store requires secure connections between your app and your server, and between your server and the App Store. For more information, see [Validating receipts with the App Store](https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/validating_receipts_with_the_app_store?language=objc).
Copy file name to clipboardExpand all lines: docs/inappbilling/changelog.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,31 @@
1
+
### 2025.07.25 [v17.1.0]
2
+
3
+
```
4
+
## Major Update
5
+
6
+
This latest update integrates **Google Play Billing v7** bringing support for **Android API v35**. (This is a required update before the end of August 2025.)
7
+
8
+
**This release brings a refactoring of the extension around products and purchases events.** The purpose here is to reduce the ambiguity of the `InAppBillingEvent` that was previously used to handle all events and to provide a more consistent API for handling purchases and products.
9
+
10
+
This update also includes a major update to the **Samsung IAP** integration. The SDK has been updated to v6.4.0 which includes a range of internal changes. Purchases now need to be acknowledged which is completed when through the normal process of calling `finishPurchase()`. There have been some internal changes to offers with usage of the "promotion eligibility" checks that are performed when retrieving the product list.
feat(playbilling): update play billing sdk v7.1.1 (resolves https://github.com/distriqt/ANE-InAppBilling/issues/649, resolves https://github.com/distriqt/ANE-InAppBilling/issues/647)
18
+
feat(samsung): update samsung iap sdk v6.4.0
19
+
feat: refactor introducing separate product and purchase events to provide clearer usage
20
+
feat(package): update package files to include supported platforms
21
+
feat(android): update `nativeVersion` function to return version of billing service (after setup call)
22
+
feat(playbilling): add ability to set new EU requirements on purchase requests (`isOfferPersonalised`)
23
+
feat(playbilling): add `PendingUpdate` details on a purchase when purchase is changing
24
+
feat(playbilling): add `SubscriptionInstallmentPlan` on a `SubscriptionOffer` for subscription installment payment options (resolves https://github.com/distriqt/ANE-InAppBilling/issues/606)
0 commit comments