I have added the accounts of some Google Play users to email lists for testing purposes, as shown in Image 1.
When I apply the email list for internal testing of an app, these test users can purchase in-app items of the app without actual deductions, as illustrated in Image 2.
However, I’ve noticed that Google Play users included in the testing email list can purchase all in-app items across all my apps without actual deductions. Isn’t this an unusual scenario? Something seems off.
5
Answers
For paid apps, if you are using an internal test track, than anybody on the testing email list can install it for free. If you are using an open or closed testing track instead, even those on the testing email list will have to pay for the app. Though I have not done in-app-purchases myself, I would assume that it functions the same way. I would recommend trying to use a closed or open testing track and see if your testers will have to pay for in-app-purchases then.
From the Google Play Console docs:
It seems like there might be an issue with the testing configuration or settings for your apps on the Google Play Console. Without specific details, I can offer some general guidance:
Firstly, Check Google Play Console Settings:
Review the settings on the Google Play Console for your apps, particularly those related to testing and in-app purchases. Make sure the testing accounts are properly configured and limited to the specific app you are testing.
Then, Ensure Proper App Configuration:
Verify that each app is correctly configured to handle in-app purchases. It’s important to set up in-app products and their pricing appropriately for each app.
And,Separate Testing Environments:
Google Play Console allows you to create different testing tracks, such as internal testing, closed testing, and open testing. Make sure you are using the correct track and that the testing accounts are associated with the appropriate track.
Next, Check In-App Billing Library Implementation:
Ensure that the in-app billing library implementation in your app’s code is correct and that it distinguishes between testing and production environments. The testing environment should not deduct actual funds from users.
And then Review Google Play Policies:
Make sure that your testing practices comply with Google Play policies. In some cases, unusual behavior or testing practices may be flagged as policy violations.
Finally, Contact Google Play Support:
If the issue persists and you cannot identify a solution, consider reaching out to Google Play Developer Support for assistance. They can provide guidance on any specific issues related to your account or app configuration.
It’s
important
to thoroughly review your settings, configurations, and implementation to ensure that testing accounts are appropriately restricted to the intended app and that in-app purchases are handled correctly during testing.Have you reviewed the licensing testing? If not, kindly take a moment to check and make any necessary adjustments from there.
I think it is one of three scenarios:
This should not happen, use a fresh email on a fresh phone that you’ve never used before add it to a new list and add this list to one app only then test on other apps, you will find out that you can not get any paid item for free.
Google Play users who are
whitelisted
aslicense-test
in the Play Console can make purchases without being charged. This is for general testing and when the app goes to QA.