Internal testing in Google Play doesn't send out emails - android

I have successfully uploaded my APK to Google Console and set my own email adress as tester for internal testing. But when I Submit the app for internal testing I don't receive any mail. As you can see the email is correct and the APK has been uploaded correctly. Have I missed a step or done something wrong? Don't understand.

You need to share the opt-in link to your internal tester manually:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
Copy the "Opt-in URL" to share with your testers.
Once your tester have opted-in they will see the alpha/beta build on play store as soon as play store has published it.
Moreover the email addresses used should by the ones of the Google Account your testers use on their mobile phones.
Step 3: Share your opt-in URL with users After you create a test,
you'll get a URL link to your app to share with your testers. The
opt-in link only shows when an app is "Published." Apps in "Draft" or
"Pending publication" won't show the opt-in link. 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. If you're running a closed test with a Google Group or
Google+ Community, users need to join the group or community before
opting in to your test.

I had a similar problem and it turns out I created the internal release by hadn't published it I guess.
The solution was to click the "Create Release" button at the top of the internal test page under "App releases". I hadn't clicked that button originally because I thought it would advance my app from internal release to release to the general public. Basically I got confused by the label.

Related

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.

publishing an alpha vsersion of my android app

I am confused about android application testing. when I publish an alpha version, do all the people who are registered as testers in the whole world have access to the app or do I get a link and send it to whoever I know to test it. if its the latter how can I get testers for my app.
Alpha and beta tests are working in the same way. You upload your app to google play, fill out all the fields in your store entry and then you need to create a Google Plus community. Copy and paste the URL of the community into the Google Play developer console as testers, you will see another URL2, this URL2 has to be opened by your testers. Now you need to find people joining your group in Google Plus and tell them the procedure for tester:
Open URL2
and confirm to participate the testing
The installation has to be started with a browser, the URL of your app is the same as for apps in production.
If you ship a new alpha version, your testers get the new version automaticly if they have configured that.
From here on everything is as it is for apps in production.
I agree it is a kind of an odd procedure and I hope I explained it clear. However, what you can always do, just upload your apk to a web server and provide your testers with the link for the app on your webserver, your testers only need to accept installations from third party. You can't get ratings for such an app.
Later what you said only will work out in alpha testing, you should have separate testing team in your organization so that you can share the URL with them to test the app or you can add them using their google play account so that the app will be visible only to them in their Google play app, not to all of the real time users.
Until you upload the apk in production mode, your app will not be visible to other users.

play store alpha test download link not working

I think I followed all steps which I have found so far but the download link for my alpha test isn't working.
I uploaded the app 3 days ago, created a google group and added the group to the list of alpha testers.
I invited a few members and the app status shows published, after clicking on the link I can signup as alpha tester, but when I click on "Download from the Play Store" the error message "We're sorry, the requested URL was not found on this server" comes.
Did I miss an additional step? Do I have to grant some special rights to the group members somehow?
--- update can this be caused by the permissions of the app?
under the apk info in the developer console I can see:
functions:
android.hardware.LOCATION
android.hardware.location.GPS
android.hardware.location.NETWORK
android.hardware.TOUCHSCREEN
permissions:
android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.INTERNET
-----UPDATE2
Well I don't have any idea what changed but now the download link is working for my alpha testers.
For me, it resulted to be a cache problem so deleting the cache in Setting > Apps > Google Play Services > Storage > Clean Cache and deleting chrome's cache, did the trick.
If your app is published in alpha or beta version :
it won't be shown in search results,
use the link that google play sent you in the group of testers in order to open it in Google Play application.
(see edit below)
You can also open this URL : https://play.google.com/apps/testing/APP_PACKAGE with a browser if the email configured in your phone is a member of the google testers group.
i don't think permissions in manifest can hide an app of the store !
EDIT
After you have uploaded your APK file and published it to Alpha or Beta version, you will see a link "manage testers group" or something like that. Click on that link ... you will be asked to add a google group of testers, below the popup you will see a message like this : "share this link with you testers group". Copy that link and send it to the group by mail.
Sorry I am writing with SO android app, I can't paste screenshots therefore ... may be tomorow ;-)
Hope it's ok.
I don't have any idea what changed but now the download link is working
You issue was just the publish delay -- it takes some time for Google Play servers to pick up your submission (for any publishing operation, even with alpha builds), usually under 24 hours.
Try opening the link on both your test device and in a desktop browser.
I was able to sign up as a tester from the device, but not install the app (said not found), but going to the desktop browser was able to use google pay to install it remotely to the device.
Make sure its the url in the form https://play.google.com/apps/testing/{your.namespace}
Sign in to your Goole Play Console.
Select your app.
On the left menu, Select Release management -> App releases.
Select Manage Alpha or Manage Beta.
Manage testers, click on right side down arrow.(Just below CREATE RELEASE)
Choose a testing method: select Closed Beta Testing.
Next Create list or select the name of your list.
Feedback Channel: Enter your email to get feedback from testers.
Copy Opt-in URL and send it to your testers.
Now once you completed, Google Play servers takes time for any publishing builds alpha or beta. For me it takes 15-20 minutes to available.
Sometime clear cache of your browser and refresh link. will work.
Once link is available, Open it in your testing device and click on below link
Download the *APP NAME* app on Google Play
Press the Update Button. After installation you can test it.
How authorized testers turn on internal app sharing
Before authorized testers can download apps using internal app sharing, they need to turn on internal app sharing on their Google Play Store app.
Open the Google Play Store app Google Play.
Tap Menu Menu > Settings.
In the “About” section, tap the Play Store version 7 times.
After the Internal app sharing setting appears, tap
the switch to turn on internal app sharing. Tap Turn on.
I'm having the same problem, the link simply doesn't work, 36 hours after publishing. Might as well not even provide the alpha/beta features if it's going to be like this.
Anyway, I'm sharing some information provided to me by Google Support, hoping it'll be helpful:
Ensure that you have added a valid Google Group email or Google+ Community URL to the Developer Console and that you are included in the group/community. Once the group/community has been added, the name of the group will display in the “Manage list of testers” link in the testing tab. (Please note when adding a Google Group you need to enter the email address and not the URL).
If you wish to use a Google Group in a Google Apps domain, the Developer Console and Private Channel must be enabled for your domain in the Google Apps Control Panel.
An app must be published for several hours before the opt-in link will become available to testers.
Currently, testers must have only one account on their device. Devices with more than one account will receive the production version of your app. (Please note this requirement is temporary. Stay tuned for updates).
If you followed the mentioned instructions and it's still not working, in 2019 make sure to also check the following:
1) Make sure the testing group is selected, but is also active:
2) Ask your testers to log out of their google account, then to clear the cache of their browser. They should then close/re-open the browser and log in into the invited email address.
There are several causes for the internal/alpha testing link not working:
1-You are on a different google play account
2-Your email is not added at the email list for testers
3-Go to google play console> your app > app releases > internal test > make sure list name is check as if not the testers will not have access to the app
Hope this helps to solve the issue
One of the causes of that issue might be its availability in (one) particular country only. (USA, usually).
In that case you just should go to the app details and allow its distribution to other (local) stores.
My problem was that even though I deinstalled my release version the link from internal testing brought me again to the release version. This fixed it.
I had this problem if I was logged in with multiple different Google accounts. I opened a new private browsing window and logged in with the account that I wanted to use as an alpha tester, and then the download link worked.
I got the same issue, seems a bug. Solved by:
1.Click "unpublish".
2.Wait for a while, click "re-publish".
Then my App became available in a few minutes.
In my case I was listed as tester in several list (alpha and internal test).
I had only joined the alpha testing channel and I had no way to access the app via the link nor via searching the store.
And as soon as I also joined the internal test channel.
The link to the app magically started working.
So I guess the rule is: you need to make sure you have joined the most privileged testing group that you're invited to.
Also make sure the app, you're going to test, is uninstalled from your device.

How to distribute apk to limited users. And they cannot re-distribute to others?

How to distribute apk to limited users. And they cannot re-distribute to others?
One way to do is get device IMEI number and post to server to check valid user or not. But I am trying to limit in android code itself to avoid server communication.
Also as I will not publish app on google play,I am not able to add Google Play Licence Verification library.
Use Beta-Testing section from Play Store, after uploading your apk on Play Store. You can create a group of user from Google+ and add them in testing section. Follow this :
Create an App
Log into the Developer Console and upload an APK. No need to publish it yet.
Check out the ‘Beta’ tab now, which should show this handy message:
Upload Beta APK
Click the Beta tab and upload the APK again. Publishing from this tab will not push it to the store, but there is a handy button that allows you to promote apps from Alpha to Beta to Prod, which is neat.
Create a Test Group
Using your developer account (it must be the primary google developer account), create a Google+ Community. Public or private, doesn’t matter. (You could use a Google Group too, but Google+ is a pretty good medium for wrangling a beta team, so I’ll recommend it here.)
Add your Community to the list of testers by clicking “Manage list of testers” and pasting the Community’s URL.
Invite Users to Test
Click publish in the Beta tab. Click again on “Manage list of testers” and there you will find a URL to share with your Community. When they go to that URL, they’ll get a signup prompt (later, a play store link). Roll outs will take anywhere from a minute to a couple hours to propagate, as with anything on the store.
Hard code the list of IMEI or device IDs in the app. On launch check the device ID against your white list and either launch or kill the app depending on the result.
You can roll out a version to a limited amount of users through the play store.
Just have to create a google Group or a Google+ group and follow the instructions here:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en

Google Play Alpha/Beta testing link is broken [closed]

I have developed my app and have published it through Google Play for alpha testing. As one of the testers I get an opt-in link, where I signed in as a tester. After that I was hoping to download the app directly with my phone by going to the Play Store on my phone. But as it seems to turn out, I have to got to the app's web profile and then from there click download; only then does the Play Store download the app to my phone.
I want to get other alpha testers involved and I was hoping to make the process easier for them. Is there an easier way? As in, once they opt-in, I would like them to just use their Android phone to download the app the way they would any other app. Is there a way?
Clarifications:
I am not looking for an alternative to Google Play
I have already gone through the Google Group creation process. My question is concerning what happens after a group member opts-in. Can they use their phone directly (play-app on phone) or must they download from the website? So far I have not been successful using the play-app.
You need to publish the app before it becomes available for testing.
if you publish the app and the apk is only in "alpha testing" section
then it is NOT available to general public, only for activated testers in the alpha section.
EDIT:
One additional note: "normal" users will not find your app on Google Play, but also the activated tester can not find the application by using the search box.
Only the direct link to the application package will work. (only for the activated testers).
Here is a check list for you:
1) Is your app published? (Production APK is not required for publishing)
2) Did your alpha/beta testers "Accept invitation" to Google+ community or Google group?
3) Are your alpha/beta testers logged in their Google+ account?
4) Are your alpha/beta testers using your link from Google Play developer console? It has format like this: https://play.google.com/apps/testing/com.yourdomain.package
Publish your alpha apk by pressing the submit button.
Wait until it's published.
(e.g.: CURRENT APK published on Apr 28, 2015, 2:20:13AM)
Select Alpha testers - click Manage list of testers.
Share the link with your testers (by email).
(e.g.: https://play.google.com/apps/testing/uk.co.xxxxx.xxxxx)
It should be noted that releasing an alpha app for the first time may take up to a few hours before an opt-in link is available and invitations are sent out to the email addresses in your testers list.
From Google support:
After publishing an alpha/beta app for the first time, it may take a
few hours for your test link to be available to testers. If you
publish additional changes, they may take several hours to be
available for testers. [source]
You may want to wait until you have an initial opt-in link before publishing more changes to the app because doing so is likely to increase your wait time for receiving your tester link; or, may lead to your testers testing with the incorrect version.
Hope that clears things up for anyone confused about why they don't have an opt-in link as depicted in screenshots in this SO thread!
Under APK/ALPHA TESTING/MANAGE TESTERS you find:
Choose the method you want.
Then you need to first upload your Apk. Before it can be published you need to go to the usual steps in publishing which means: you need icons, the FSK ratings, screenshots etc.
After you added it you click on publish.
You find the link for your testers at:
Google play store provides closed testing track to test your application with a limited set of testers pre-defined in the tester's list known as Alpha Testing. Here are some important things to be considered to use alpha testing.
Important
After publishing an alpha/beta app for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers
Managing Testers for Alpha Testing
The Screenshot is most recent as of answering this question. You can see the manage testers for closed alpha testing, You can add and remove tester one by one or you can use CSV file to bulk add and remove. The list of defined email addresses will be eligible for testing the app, here you can a control whom to provide the app for testing. Hence, this is known as Closed Testing.
You can see the link(washed out by red line), once your app available to test, your testers can download and test the app by going to the below-given link. For that Google will ask once to the tester for joining the testing program. Once they have joined the program, they will receive an app update. As stated by store, it may take 24 hours to make an app available for testing.
Once your app available, Your invited testers can join the test by going the link https://play.google.com/apps/testing/YOUR PACKAGE NAME
Managing App Releases
After the Manage testers card, there is a card for manage release, from here you can manage your alpha releases and roll-out them to production by clicking the button at the top of the card once they well tested. This process of rolling out from testing to production/public is known as stagged roll-out. In stagged roll-out, the publisher publishes by the percentage of users, to better analyze the user response.
You can also manage multiple alpha release app versions from here, at the bottom of the screenshot you can see that I have once more apk build version being served as alpha test app.
Managing Closed Track Testing Availability
Apart from the user based control, you have one more control over the availability of the app for a test in the country. You can add limited countries tester to the app. suppose your list of the testers are from multiple countries and you want the application to be tested in your country only, rather removing testers from the testing list, you can go through Alpha Country Availability. It gives more precise control over testers.
Here, In Screenshot, my app is available worldwide states that my testers (from testers list) can test the app in all countries.
In my experience the flow is:
you publish the app as beta in Google Play and create the Google+ community
invite the tester to the community
once he has joined, send him the link of the test app in Google Play
the tester opens the link in the browser (not google play app)
registers as tester
in the browser, install the apps to the device (the app will be magically pushed to the device)
Another issue of that page if you use multiple playstore accounts:
In some cases you still get a 404, even if you are currently logged in with the right account, the one you joined the beta community with.
As a workaround, you can clear the browser cache, use another browser for the beta signup, or just use the incognito mode of your browser.
You can use a Google Group and have your alpha testers just join the group. Everything else should just be handled through the Google Play Store App.

Categories

Resources