Develop Reference

How to submit PlayStore app access credentials for google sign in authentication

I have an app where a user needs to log in with a google account & purchase premium (play billing) for accessing premium features. Everything works perfectly.
Recently playstore force developers to submit app credentials to test if the app has certain functions which require authentication.
If my app has a normal email and password for auth then I'll submit to google play a test user's e-mail and password from my backend server. But now It's Google Sign in. I don't know any test google account which uses app reviewers. The doc has no information about that.
In this situation, should I have to submit my personal google account and password to review app authentication (because it was added to the test licence in the GooglePlay developer console)?
or there is some test google email account from (playstore app reviewer) for whitelisting on my server-side?

You Just need to tell them to "login using Google Account" in "Any other instruction" field, as shown below, you don't have to create a test account for this. I tried this many times before.

So I was stuck on this issue for about a whole month, I couldn't update my production app.
Google documentation clearly state that Note that you do not need to provide credentials if your app supports "Sign-in with Google,” which enables the crawler to log in automatically. However this was not the case for me.
I tried:
Going with the 1st option that - No special access is required. - Never worked
2nd option - Stating the the app requires Google login (didn't submit any credentials). - Never worked
Eventually, what worked was - I created another email account on my mobile device. Then submitted the credentials to Google.
Point to note - ensure the email account you create doesn't contain any 2 factor authentication or verification as this won't work.

I noticed that you do not need to do this in the case of a Google account.
If you see the pre-launch reports in the Google Play console, and watch the replay of the test, you will see that when the Google Play robot encounters the Google Account login screen, they will have an account with a #cloudtestlabaccounts.com email that they will use to login as seen on the below image:
As you can see, Google Play robots have Google accounts available to them to login and therefore you do not need to put as special access, unless if you are using non-Google accounts to login.
I personally use Google Accounts as login and never submitted any login information and they didn't have any issue with this.

I created a Google account specifically for app testing purposes. I use it for both Android and iOS. You submit the credentials for that account for review. After your app is approved, you can always change the password and just update the credentials when you submit the app for review again.

I tried submitting use "google login" in any other instructions field but it didn't work.
What worked was I created a demo google account and submitted the email and password. Also, wrote use "google login" in any other instructions.
hope it helps

Which means " Gmail accounts with testing access " in google developer console

what is in google developer console:
License Testing
In addition to the owner of this console the following users will get the License test response from the application. There is a limit of 400 test accounts.
Gmail accounts with testing access
License Test Response
All accounts listed above will get the License Test Response. The account owner (but not the other test accounts) will also get this response for applications that have not been uploaded to Google Play yet.
I can not find anywhere else to describe why and how to use it.

You can find it in Google Play Console->Settings->Developer account->Account details->License Testing. If you create an In-app Billing application, this area allows us to make a test order with a free purchase. For example, your google play account e-mail is "abc#gmail.com" and if you enter in license testing area, google allows you to buy item for free. By the way, you should upload your release apk to beta release field in google play console.

Android in app subscription testing

I want to test the in app subscription mechanism on android devices(In app billing V3. api).
How can I do this? I saw that testing with static responses is works only with the in app products. The beta/alpha testing supports the in app subscriptions?
Thank you.

You can test your app with in app purchase feature. you have to follow below steps for testing
Upload you final signed apk file to Google play.
Dont publish it
Add in app products
get in app products id and add to code
get base 64 key and add to product
sign apk and upload again
your app should be in draft mode
in you Google play account setting add your test account id
use the device which should have the primary account id similar to the one you have added on Google play test account.
Install signed apk you have uploaded to Google play to your device.
run application and test your features

Since there's no effective way to test subscription cancellation/renewal, I'm trusting Google's documentation that an expired subscription won't appear in purchased items (otherwise, whether cancelled but still valid, original or renewed, I don't care in my case).
To test the rest of my work flow I created a test consumable object so that I can re-buy/cancel it at will in the sandbox. This consumable simulates an active subscription. It's not full end-to-end testing, but given that Google's given us no better way to test subscriptions, it will at least give me a fair amount of confidence that my app behaves as expected, otherwise.
A few notes:
1) You can only test with a signed build. I added android:debuggable="true" to my AndroidManifest.xml (under
<application android:debuggable="true"...)
2) This way I can still connect and debug with breakpoints after installing via adb (you can attach to the process under the Devices view, normally visible in the DDMS perspective, look for the little green bug icon.)
So far, it's behaving as expected. I'm still in the process of testing but if I hit any snags I'll update.

In adittion to #Vaibhav-Agarwal if you only want test your app, you could have problems with the IDs (I have experienced with an app for a client).
In my case, to avoid this situation, I had to add a testing project with another special package (test.xxxx.xxxx.xxxx) and here add some in-app product with a trial of 7 days, then when I canceled a purchase I "only" had to wait 7 days to purchase again this subscription.
In this way also,you never had to make a refund, because the subscription with trial time, you haven't to pay until this trial time finish.
NOTE:
Draft Apps are No Longer Supported, you must use Alpha/Beta tester option
In spanish, you will read: "no se ha podido encontrar el elemento que intentabas comprar"

Google has been enhanced theirs In-app Billing testing options. I write this answer for those who coming through . Now, you can test In-app Billing in Sandbox as other platforms do. In order to do that you have to create license test accounts for authorized users.
In the Developer Console, go to Settings > Account details, then in the License Testing section, add the addresses to Gmail accounts with testing access field.
Notes :
Test subscription purchases recur daily, regardless of the product's subscription period.
Once you’ve added the users as license tester accounts and saved the change, within 15 minutes those users can begin making test purchases of your in-app products.
After you publish your app to an alpha or beta channel, your testers need to opt-in to your app’s alpha or beta test using the provided opt-in URL before they can make test purchases.
License test accounts must be on the user’s Android device. If the device has more than one account, the purchase will be made with the account that downloaded the app. If none of the accounts has downloaded the app, the purchase is made with the first account. Users can confirm the account that is making a purchase by expanding the purchase dialog.
For more visit the official documentation.

But you can test Google Play functionality with an unpublished app using static responses.

Can I turn my own Google Play account into a test account without any problems?

I'm developing our first app that uses in app purchases, and need to test that it's working correctly.
Currently if I try to make a purchase on the "android.test.purchased" item, I get an error message back saying "invalidClient". I'm led to believe that this is because my account is not a test user.
I found this page:
http://developer.android.com/google/play/billing/billing_admin.html#billing-testing-setup
which tells me how to set up a test user. I could set up a new user account, but I only have the one Android device to hand, which means doing a factory reset to make this the primary account, and I'd rather avoid that if possible.
Alternatively, can I make my own personal account double up as a test user?
The link above says that test users have limitations, one of which is:
Test accounts can only be used to purchase items that are listed (and
published) in an application's product list.
That seems to imply that I could only use my account to buy things in my in-development apps, and not from other apps as normal.
So can I turn my own personal account into a test user, without any problems when using the account to purchase other apps as normal?

It won't affect your abilities to use the test account as a normal account for other apps on Google Play.
So simply you can use your own account as a test account. (Actually if your account is the publisher account, you don't need to add it as a test account.)
The limitations mentioned in the documentation is a comparison to the publisher account.

Unfortunately there's no way around it. If you just have one device you have to wipe the device and then first sign in with the email address that you want to use as a test account. Only then will you be able to test in-app billing. You can also download other items from the Google Play store. I've done this without any problems.

Testing Android In-App purchase with real products

im trying to test In App purchases for my android app:
I already read the android developer sites about testing and I already have worked successfully with the play stores build in test/fake product-items like android.test.purchased, android.test.canceled ...
Now I would like to test In App purchases with my own real products. Therefore I have specified my own products in the Google Play Store Developer Console.
My question:
According to the android developers guide, it should be possible to buy this real item without transferring real money, by simply adding a gmail Account into the App settings (under the section LICENSE TESTING) in the Play Store Developer Console.
LICENSE TESTING
In addition to the owner of this console the following
users will get the License test response from the application. They
can also make in-app purchases from APKs that have been uploaded but
not been published yet.
So if login to google play store on my test device with a gmail account, that I have added to this LICENSE TESTING section, I should be able to buy items, without transferring real money? Did I get it right? Has anyone experience with testing in app purchases and can give me some useful advises?

From my recent experience.
With a different gmail account from the developer it is possible to buy in app purchases which are published for an app that has been uploaded but not published. You have to exchange real money but it is possible to refund the money. I think you would lose the 30% transaction fee to Google.

Don't know if this is relevant, but here's a good guide for testing purchases, including test purchase accounts in google:
http://developer.android.com/google/play/billing/billing_testing.html

With a test account the IAP will not be charged.
http://developer.android.com/google/play/billing/billing_testing.html
"Test purchases and developer account
Authorized license test accounts are associated with your developer account in Google Play, rather than with a specific APK or package name. Identifying an account as a test account enables it to purchase any of your in-app products without being charged. "