Google Play You Are Already Uploading From Two Accounts
Y'all should be testing your integration throughout development. To test during the development phase, we recommend leveraging license testers to run through the scenarios described in this topic. To configure license testers, encounter Test in-app billing with application licensing.
Using license testers provide the following benefits:
- Usually, the Google Play Billing Library is blocked for apps that aren't signed and uploaded to Google Play. License testers can bypass this check, meaning y'all can sideload apps for testing, even for apps using debug builds with debug signatures without the need to upload to the new version of your app. Annotation that the package name must friction match that of the app that is configured for Google Play, and the Google account must exist a license tester for the Google Play Panel account.
- License testers have admission to examination payment methods that avert charging the testers existent money for purchases. Y'all can as well employ test payment methods to simulate certain situations, such as when a payment is declined. Figure one shows these exam forms of payment as they announced within the purchase flow.
- License testers tin rapidly test subscription features.
Here are some additional details about the test purchase process:
- Test purchases utilise the aforementioned app purchase menstruum used by bodily purchases.
- Taxes are not computed for exam purchases.
- Google Play indicates a test purchase by displaying a notice across the center of the buy dialog.
You can ostend the account that is making a purchase past expanding the buy dialog. Annotation the post-obit:
- Test accounts must be on the tester'south Android device.
- If the device has more than i account, the buy is fabricated with the account that downloaded the app.
- If none of the accounts have downloaded the app, the purchase is fabricated with the start account.
Before distributing your app, you can make use of Google Play test tracks to perform boosted validation. For case, yous can leverage test tracks to take your QA team qualify a new release.
With exam tracks, users tin install your app from Google Play and examination a version of your app that is non withal publicly available. Users tin make real purchases using whatever of their payment methods in Google Play.
To test your Google Play Billing Library integration using test tracks, exercise the following:
- Publish your app to a test track. Note that after y'all publish an app to a testing rails, it can take a few hours for the app to be available for testers.
- Ensure each tester opts-in to your app's test. On your test'south opt-in URL, your testers see an explanation of what information technology ways to exist a tester forth with a link to opt-in.
You tin exam your integration on any Android-powered hardware device running Android one.half-dozen or higher. The most electric current version of the Google Play awarding must be installed on the device. For general data about how to ready a device for utilise in developing Android applications, come across Using Hardware Devices.
Exam one-time products
Examination consumable products
When testing consumable products, we recommend testing a diversity of situations, including the following:
- A successful purchase where the user receives an item. With a license tester, y'all can utilise the Test instrument, always approves payment method.
- A purchase where the payment method failed to be charged, and the user should non receive the particular. With a license tester you can use the Test musical instrument, ever declines payment method.
- Ensure items can be purchased multiple times.
Yous should as well verify that purchases are properly best-selling as described in processing purchases. For purchases from license testers, a purchase volition be refunded after three minutes if your app does non acknowledge the purchase and you lot will receive an e-mail nigh the cancellation. You can also check the Orders tab in the Google Play Panel to see if an gild was refunded after 3 minutes.
Test non-consumable products
Non-consumables should exist tested the same as consumables, simply you should verify an item cannot be purchased again within your app. Exist sure to verify purchase acknowledgement for both not-consumables and consumables (when applicable) since the logic to process each the two types of purchases vary.
Test pending purchases
You should test a pending purchase where the item should be granted when the purchase state becomes PURCHASED. License testers have access to two test instruments for delayed forms of payment where the payment automatically completes or cancels after a couple of minutes.
-
Make a buy with a delayed form of payment "Slow test menu, declines later a few minutes", as shown in Figure two. Restart the app, validate that the purchase has not been granted.
Figure 2. Test a buy with a declined tiresome test card. -
Brand a purchase with a delayed course of payment "Slow examination card, approves after a few minutes", as shown in Figure 3. Wait a few minutes, validate that the purchase has been granted.
Effigy 3. Test a buy with an approved slow test carte du jour.
You can find more information at Treatment pending transactions.
Examination subscription-specific features
The purchase flows for 1-fourth dimension products and subscriptions are like, only subscriptions accept additional scenarios, such equally successful or declined subscription renewals. To test renewals, yous can use the Test instrument, e'er approves and Test musical instrument, ever declines payment methods that are available for license testers, as shown in figure 1. Apply these payment instruments to exam scenarios beyond the successful subscription scenario.
Similiar to one-time products, you should also verify that purchases are properly acknowledged equally described in processing purchases. For purchases from license testers, a purchase volition be refunded after iii minutes if your app does not acknowledge the buy and you will receive an email about the cancellation. You can also cheque the Orders tab in Google Play Console to see if an order was refunded after 3 minutes.
Renewal periods
Exam subscriptions renew more quickly than bodily subscriptions, and test subscriptions can renew a maximum of 6 times.
The following table lists the testing renewal times for subscriptions of various durations. These times are estimate. You may run across small variations in the precise fourth dimension of an event. To compensate for variation, call the API to view the current status later every subscription expiration appointment.
| Product subscription period | Examination subscription renewal |
| 1 week | 5 minutes |
| 1 month | 5 minutes |
| 3 months | ten minutes |
| 6 months | 15 minutes |
| 1 yr | thirty minutes |
Time-based subscription features such as free-trials are as well shortened for testing. The following tabular array identifies the testing fourth dimension periods associated with fourth dimension-based subscription features:
| Feature | Test period |
| Purchase acknowledgement | 5 minutes |
| Free trial | 3 minutes |
| Introductory price period | Same as subscription exam period |
| Grace period (both 3- and 7-day) | 5 minutes |
| Account hold | x minutes |
| Pause (1 month) | 5 minutes |
| Pause (2 months) | 10 minutes |
| Pause (3 months) | xv minutes |
Test Cases
Expand the post-obit section by clicking Show/Hide to show testing scenarios you should use to verify your subscription integration.
You can employ the Google Play Panel to create codes for your own testing. Keep in listen that yous may merely create 500 promo codes per quarter beyond all managed products in an app.
Y'all should exam the following promo code redemption scenarios:
- When the promo lawmaking is entered in the buy dialog that was launched within your app.
- When the promo code is redeemed in the Google Play Store app.
- When the promo code is redeemed at https://play.google.com/store using the Redeem button in the left-hand navigation.
Within these scenarios, you should examination redeeming codes in every bit many means as possible. We recommend perform the following tests at a minimum:
- Redemption earlier the app is installed.
- Redemption while the app is running in the foreground. Notation that for this test, you lot need some other device to examination using the Google Play Shop app. Be sure to test redemptions from different screens in your app.
- Redemption with multi-window mode, where both your app and the Google Play Store app are existence displayed at the same time.
For each test, make sure that the item is correctly detected and that the user is notified.
Source: https://developer.android.com/google/play/billing/test