From 98a11580ef889fd2fa8ecd6f8fb3d23c77469125 Mon Sep 17 00:00:00 2001
From: Kevin Hufnagle
Date: Thu, 23 Jun 2016 20:32:08 -0700
Subject: docs: Added note - test subscriptions cannot use reserved IDs
The "Testing In-app Billing" page now includes a note which explains
that test subscription purchases must use real purchase IDs, not
any of the IDs reserved for testing one-time in-app purchases.
Bug: 27352434
Change-Id: I625178c3517ce9940bc4746d99f1d506fd5e944b
---
docs/html/google/play/billing/billing_testing.jd | 9 +++++++++
1 file changed, 9 insertions(+)
(limited to 'docs')
diff --git a/docs/html/google/play/billing/billing_testing.jd b/docs/html/google/play/billing/billing_testing.jd
index 44b7ad3081cf..22480a2d0b77 100644
--- a/docs/html/google/play/billing/billing_testing.jd
+++ b/docs/html/google/play/billing/billing_testing.jd
@@ -199,6 +199,15 @@ reserved product IDs. Also, you cannot specify the form of payment when you make
with a reserved product ID. Figure 1 shows the checkout flow for the reserved item that has the
product ID android.test.purchased.
+
+ Note: If you're testing subscription purchases, you must use
+ the product ID of an actual subscription, not a reserved product ID. To verify
+ that Google Play is processing the test subscription purchases correctly, you
+ should
+ set
+ up test accounts for your app.
+
+
Figure 1.Purchase flow for the special reserved item android.test.purchased.
--
cgit v1.2.3