Develop Reference

How to invite Google Play Console internal testers

Releasing an app on Play Console has several release steps: internal testing > closed alpha > open beta > production
I'm in internal testing phase, but no one on my testers list has been given an invite. I created the list, including my email and another that I know is valid, both Gmail accounts, but no email invite. There is an option to "save" after managing testers, but there is no "send invite" button. All I missing something?

The system doesn't invite them, you have to give them the opt-in URL yourself. I think the email list is just for access control.
The Google Play Console Help details this step:
After clicking the opt-in link, your testers will get an explanation of what it means to be a tester and a link to opt in. Each tester needs to opt in using the link.

Here's what worked for me:
Go to "App releases"
then "internal test track"
then "manage Manage testers"
then click "expand"
the "Opt-in URL" appears as in the image below
send the link to all testers, they'll be able to "join the programme"

I ran into this same problem today. I added myself to the internal testing and waited for the email, it never came. There's no indication on the web page or documentation that it is supposed to come.
BTW, I've had great success with Fabric Beta for distributing test versions of my apps before. I've also been involved with a project that uses Microsoft's App Center -- that seems to work pretty well too.

In my case the mailing list wasn't checked, I missed that!

Well, I had the same issue and what I did the followings:
Option 1: I sent the Google Play app link: by which they can directly go and download the Internal Tester version
Option 2: And, I manually sent them the .apk file which they manually downloaded and install. And the internal testers are happy with it.
NOTE: Try option2 only if Option-1 does not work.

How to cancel a pending publication on Google Play Developer Console?

Is there a way to cancel a pending publication on Google Play Developer Console? I have accidentally sent a wrong apk file and couldn't find a way to cancel it.

I'm too late, but it helps someone.
If the app is under review, upload the original or new APK. Google will automatically publish the latest version. Make sure that the new APK has higher Version Code.
If you don't want to upload a new APK file, you can control when updates are published.
Log in to your Play Console account and click on the "Publishing overview" item on the left pane. Next, click on the manage button.
Select the first option.
Google doesn't publish your app immediately.

Here is a solution but it could't be posssible for me because I couldn't change my app's bundle ID.
It says that:
in Advanced Mode, you can cancel and upload again a new APK.

Item you requested is not available for purchase - android in app billing

As I am developing an application which uses in app billing, I am not able to test it using my own product ID. I have followed every step as documented on developer site. I have,
Uploaded the signed apk with release certificated to developer console.
I have published my apk to alpha channel.
I have listed my product Ids to developer console.
I have activated my product Ids and on developer console it is marked as Active.
I have listed the test account in developer console.
I have installed the same apk that I uploaded to developer console to my deveice.
The device is logged in with the test account not the developer account.
The Id that I use in my app is same as I had listed on console as per logcat message.
But, I am getting Item is not available for purchase.
Do not know what's wrong.
I know that this question has been asked on stack overflow before several times, and I have gone through each and every one of them, but none of the solutions seems to work for me so please do not close this issue as duplicate.

Found the solution for me, I had to add the testers account to alpha also. Google changed its policy, you need to be an alpha tester and not just be added to the test account list.
My steps :
Go to Alpha APK
Switch alpha testing type
Create a list
Add my tester email
Save
Submit update (top right of the page)
Wait for 15 minutes
Open opt-in url with test account and click on "Become a tester"

Just add your e-mail address to Lisense Testing
0) Go to Google Play Console
1) Go to Settings (in left drawer)
2) Go to Developer Account (and Account Details)
3) Go to section License Testing (at the bottom)
4) Add Gmail accounts with testing access
5) Save changes
Do not need any alpha release or anything else.

I am also getting this error. For this 1st generate a new signed app with upgraded version and then follow these steps
open google play console
Go to Release Management->App Release
In beta track create a app http://prntscr.com/ntxgr5
If app is create on beta track then go to production but if u click on go to production, then u getting some error like draft is full for that u have to clear the draft
In app release top most track is production track click on edit release
in left of bottom a Discard button is present click on that and remove that app
After that go to beta track and go to production and conform it
after 15-20 minute your latest app will reflect on play-store

In my case, I needed to add the e-mail (Gmail) logged in my fone.

Authentication error for Google account when installing my Application

I am able to use Google Play and download/install apps. But when I try to install my app which is already published and visible on Google Play store, I keep getting the following error:
Authentication is required. You need to sign in to your Google
Account.
I have tried it on different android devices, reset the Google account on the mobile device and re-logged in. I still end up getting the same error only for my app.
Please advice if you have encountered a similar error. Lots of remedies available when searched for the said error message but those are when all apps are not downloadable. My issue is localized only to my app.
The app(a simple game) is Android based and made with Unity.
Link to the app:
https://play.google.com/store/apps/details?id=com.CubeBoy.FlyBox

For some reason, posting the final APK to production stage straight away causes the above mentioned error.
Ensure the following:
Post your initial APK to Alpha first.
Set up a Google Group account for testing and add it under "Manage list of testers"

This article was great an is definitely bookmarked. My only suggestion is that you add the following:
Here'e what worked for me - after nearly a day of troubleshooting:
Follow this tutorial EXACTLY:
https://help.gamesalad.com/hc/en-us/articles/203536123-7-6-In-App-Purchases-IAP-for-Google-Play
Note that in this tutorial you publish an alpha testing version and add testers. Also note that the testers must have different gmail accounts than the owner of the Developer Console. So, IF THE APP IS NOT PUBLISHED, ALL TESTERS will be blocked.
If the app is published and the users are listed as testers, ensure that the testers go to the link specified in Console -> Apk Tab -> Manange List of Testers -> Share the following link with your testers. If no link is present yet, then you cannot begin testing.
If all of the above is done, then remove all accounts from your device, restart, and then add only the tester's account to the device. For example, if myTester#gmail.com then on device go to settings-> Accounts -> Google -> Click each account and select "remove account" -> Restart device -> Go to settings -> Accounts -> Add Account -> Select a Google account and enter credentials. As stated in the tutorial, this account CANNOT BE THE SAME as the Developer's Console owner.
The last check would be to try and sign into Google Play and see what account comes up. If not, the account credentials may be the issue

I had the same problem. Play also told me it was incompatible with my devices.
I used keshk's advise and posted it as a Beta version first. Then I chose to lift it over to Production. (button to the right of the version) Then it worked immediately to install it and the incompatible warning was gone.
No need to add any testers etc.
PS I don't know exactly what text is on the English version of the button as I get it in Swedish.

I make some research. That's error can display when APK version not the same than on the production. For example, production version have 0.1, you build new version 0.2. You will get that message, until upload new version to google.

Test purchase on android

I´ve succesfully implemented a purchase flow for my app.
My app is published in Alpha stage with two of my google accounts listed as testaccounts. The APK published is the same installed on my phone.
Though, when I try purchasing something I get the "Authentication is required, please log in to you google account".
So what I did was 1. removed all my accounts on my phone and re-logged them. 2.Cleared all the data of the Play store. 3.Uninstalled the latest update(Incase it was the new update playing fuzzy).
Still the same error.
Someone that can help me? Really dont want to release the app without testing the purchasing..
Thanks in advance!

If I remember correctly, I got rid of this message by creating Google Group (https://groups.google.com) and adding my test accounts there. Then go to Google Play Developer Console, Your app -> APK -> Alpha testers and choose "Manage list of testers". There, add just created Google Group, and share a link to your app (appears below) with your test account. Next, open that link from email on your test device, and follow instructions (you will need to login in Chrome on mobile).
For reference: