I'm a developer and i was thrilled when I was watching Google IO 2013 and learned about the new Beta testing feature. So I created a Google+ community and a google group and placed the testers in there (me included).
All we get (the developers and testers) when we visit the https://play.google.com/apps/testing/com.package.stuff
is this:
Is there any trick I am missing? I would really like to use this feature.
I know there are alternatives like https://testflightapp.com/ but I'd rather keep my app under this environment where I can "promote" the Beta apk to the Production phase and so on.
I had this same issue. The reason the link is not working is because the app must be published before the link will be active. I repeat the app must be published, this does not mean there must be an APK in production. On the top right of your applications developer console page there is a drop down menu that allows you to publish the app. That link will become active immediately and your app will be available in a few hours to your testers on the Play Store.
First of all you need to create or have a Google+ community.
The process is:
Create a new Google + community. It's required to have testers through Developer Console.
Register this community in Google Play Developer Console
Invite your beta testers to this community.
Wait 8-24 hours before sharing the link
Share the link with your testers
Verify that your app is published for Beta Testing
If everything is right, the link should show something like:
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 they cripple the developer's ability to move fast...
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. More Private Channel info: http://goo.gl/DLGNe
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).
2015 and the alpha/beta testing is, at best, 50% working. About 50% (23 of our 60+) beta tester never gain access to the app via the provided link. All the others have no trouble at all installing the beta app and receiving updates. No rhyme or reason. Single account on their device, some with gmail accounts, some with private email. It's a mixed bag of who gets access and who doesn't. In all cases, once they accept the invitation to join the group they have full access to the group. But they get a 404 when trying access the app. Not worth the trouble. Our fix is to give the testers access to to our private server and pass out the beta versions that way. Updates aren't automagic, but the testers can get the app hassle free
I had the same problem and alpha testers had to get into my Google Plus Community for alpha testers.
I had the same problem (404 error on tester's link), but the cause was different from the one shown in buckson18's answer: in my case the app was published, but the user didn't join the testers Google Group, although he received the invite.
After the user joined the group, the page showed correctly.
Hope this can help someone...
I was also facing this issue. The problem was that Google group was not added. Another important thing to take care is that the account being used for developer console must be member of google group being added. I couldn't find this anywhere in the documentation.
I have been using Beta testings for a couple of years and its very unreliable. Sometimes it works, sometimes it doesn't. Now they have Open Beta Testing. I tried it today for the first time, and though I followed all the instructions, but it still doesn't show the app in the app store, unless I sign in, which makes it regular old style beta testing. Its much easier and hassle free to use HockeyApp to distribute app for testing.
After wasting hours with Goolge's Alpha and Beta versions, I always end up putting my app into production so that I could keep my testers. Its already hard to convince large number of people to do the testing, and then keep asking them to go through half working or not working procedures to download the app.
I solved it by go to https://play.google.com/apps/testing/[app package] on the device and then click that link and open it with google play
One thing that seems to have worked for us is to use the "opt-in URL" the Play Store developer console provides under "App releases" which should look like:
https://play.google.com/apps/testing/com.yourappname.android
This DIFFERS than the URL you see if you're already approved as a tester and visit the app's page on the Play Store in a browser. Ours looks like this:
https://play.google.com/store/apps/details?id=com.yourappname.android
Net net, use the 1st and not the 2nd. Good luck!
It should be noted also that the link is case sensitive so if you've got https://play.google.com/apps/testing/com.someAppName - if you put https://play.google.com/apps/testing/com.someappname it'll tell you it's not available!
Related
I have been trying for several weeks now to get the Google Alpha / Beta testing functionality on the Play Store to work with no success. As far as I can tell I have followed the process but clearly something is not working from my side. I hope someone on SO can tell me what I'm doing wrong.
I have created both an Apha and Beta testing community.
I have added the Beta testing community to the Beta testing section that relates to using Google+ communities to test. My Beta testing community does have members added.
Although I have an Alpha testing community, none of the Alpha testing methods are currently enabled.
On my test device, using a Google account that is a member of my Beta testing community, I only ever see the version of my app that is currently in Prod. I have spent days waiting just in case it takes a couple of days to show up (at least a week which I assume should be long enough).
I need to test the release version because I am trying to test some inapp billing functionality that I had to change due to security warnings from Google relating to my current Prod version.
BUT: if I load the release version of the app directly (instead of downloading from the Play Store) I can see that it is seeing this account as a "test account" because when I test the inapp billing I get the correct message telling me that the subscription will renew every day but I won't be charged. However the Beta version of the app never appears in the "BETA" tab in the Play Store.
I have noticed something "strange" (possibly) in the developer console though: When I click on the "Beta Testing" tab it shows 10399 supported devices and 0 excluded devices for the Beta app. However if I click on the line of the Beta app where you can promote the app etc, the details that are then displayed indicate 0 supported Android devices. Why would this be? This seems to be conflicting information on the console.
Note: The current Prod version of my app was developed using Eclipse. I have recently converted to Android Studio and this is my first upload using Android Studio.
Where else should I be looking to get my app to appear in the Play Store
Thanks
I was just setting up the Beta testing release for the first time and couldn't make the app visible in Play Store. Found the reason in Play Console Help:
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.
After about 35 minutes the app was published.
As this might not be the issue mentioned in original question, it might help someone.
In my case I had published the Beta version and had created the testers but not linked them together. What I had to do was:
Go to manage releases
Choose a testing method - Closed Beta Testing
Then when testers list shows, make active the group of testers you would like to test the app.
Save
Get Opt-in URL link and paste it in a new tab (you should be logged in to google)
Then click at the "Become a Tester" button
You should now be a tester and ready to go.
#Important If you still can not find the app by searching in Play Store just copy the "Opt-in URL" into your tester phone's browser and you should see the app.
Hope it helps
What solved this problem for me was clearing my Play Store app data.
In my case, I had already been on the testers list for days, already accepted the invitation link, and already gotten testing working on other devices. But, the Play Store still wouldn't show the beta version of the app on this particular device.
I went to "App info" for the Google Play Store app, "Memory", then "Clear data". Then I re-opened and was able to see the beta test app.
Disclaimer: Use with caution. Clearing your app data may remove some important information. I haven't personally experienced any problems with it, but that doesn't mean you won't.
The suggestion from #Edgehog to use Open Testing solved my problem regarding being able to see my app in the Beta tab of the Play Store.
I have not found a reason yet why the closed beta testing (using emails or groups/communities) would not work.
Make sure you also check this answer
browser cache
an actual active "testing track"
We are having the same problem in my company. Currently we are investigating possibility that maybe first install on beta channel installs prod version and updates to beta channel version when first app update is released on beta channel. It is weird workflow but the comment on Play Store "Future updates will include beta versions" supports this
There are a couple of reasons why this might happen but admittedly we did not 100% confirm this.
1) One reason is that you are viewing Google Play under another account that is not on the beta tester list.
2) The other might be an issue (or feature) with the release management. Added a user to an existing closed beta release list. Changing a list does not activate or force a Save for the "Managed testers" section. After we edited another field (e.g. feedback channel) then the Save button became active and we clicked save. This might only then propagate changes. We cannot 100% confirm this was the issue we were facing but our experience points to this.
How to publish beta test-version in Android play store ?
I'm trying to allow beta test my phonegap build app in the android play store. I already uploaded a signed apk in the beta tab and added a google+ group with some users inside ... but I'm slightly surprised that I cannot find how to install or even find this app on the testers smartphones. I opted myself as user in the group but cant see a link to the app or something like that. Shouldn't the app be already visible to beta users in the app store? Or do I have to push the publish button? The info popup tells:
"Your app can only be used by your testers when it is published to Google Play.
If your app has no production APK then it will only be visible to Alpha and Beta
testers. The link that your testers can use to opt-in will be displayed here when
you have published your app."
Sounds to me that it should be published. But doesn't it mean that the beta apk will be moved to the published-area and not being then a beta any more? I'm afraid that the app will be then visible to all users in the play store not only for my beta testers.
Could someone explain me how to publish a beta for my testers only?
EDIT:
It seems that everything I need is the opt-in link that is missing. Any idea why?
In order to be able to get the link to share with your group you have to first press the "Publish" button in the upper right. After doing this you will see the link to share with users appear as brheal shows above.
I'm adding this graphic to the discussion to help clarify exactly which one to press and which to not press.
Per the discussion above I was still a bit worried about pressing the publish button. I just did it and it works.
For more clarity I thought I'd share what it looks like. After publishing your beta apk you have to wait up to 24 hours (it took mine about 12) and then go to 'Manage list of testers' in your 'Beta Testing' tab. When it's ready you will see the opt in link available to share:
This is really an issue Google should address ASAP. You enter the console hoping to find the sections but the documentation says something else altogether. I just solved this and found the link, here are the steps updated with the current UI of the console which is not matching the documentation:
Open Google Play Console
Open your app
In the left panel go to Release management -> App releases
Scroll down to Open track, Closed track or Internal test track section according to your case, click Manage
Go to the section Manage testers and click Internal test
At the bottom you will see the link if everything is properly configured and the app is published.
VERY IMPORTANT
You need to configure the internal test list, I assume that if you
are looking for the link you've already done this.
The app needs to be published, remember it takes some hours, otherwise you won´t be able to see the link.
Here are the screenshots:
Not enough points to comment, hence a separate answer.
My suggestion is to upload a new build after setting up the beta testing.
I created a new app and rolled out the Beta version of the app.
After that I enabled the "Closed Beta testing" for a list of users - alas no opt-in link was ever generated.
After scratching my head a bit I released a NEW build which generated the opt-in link immediately.
I figured that enabling the "Closed Beta testing" AFTER the Beta version was released could have caused the issue and is maybe why the UI is constructed the way it is.... just a guess.
Try and release a new build.
I just created a new app in the Google Play Developer Console. I haven't uploaded or published any beta or production APK's. I've only uploaded an alpha version.
Once uploaded (and once several hours have passed), how/where can I find the alpha version of my app? I can't seem to find it in the Google Play store on my phone.
You can provide access alpha version of app by following below steps:
Replace com.package.name with your app package name https://play.google.com/apps/testing/com.package.name (Refer this), share this URL with your testers
After you open the URL page will have an option to "Become a tester", and proceed with the directions.
Note: Only members listed in the tester group can become a tester.
I'm using alpha and beta testing features and I think they are one of the most important features of Google Play. Hope this answer helps anyone who needs to use those features:
Direct answer to your question: At Google Play, only alpha testers can see an application which is published at Alpha Testing Stage. (Also, only Beta Testers can see an application which is published at Beta Testing Stage)
Detailed steps:
At Google Play Developer Console, select your application and go
to APK section.
Select Alpha Testing tab.
Upload your apk to Alpha Testing.
At Google Play an application which is published at Alpha Testing can only be seen by Alpha Testers. So you must define alpha tester groups.
Define tester group with Manage list of testers link at Alpha Testing tab. When you click that link you'll see a panel which asks; Add Google Groups or Google+ Communities.
If you don't have a group yet, you can Create a Google+ Community and add people to that group with
their google/gmail accounts.
Testers are going to see your application at Google Play if they are
logged in with the same google/gmail account which they are added as
tester.
NOTE: Process is same for Beta Testing. Just define another tester group and add testers to it.
I was wondering this myself when I saw that this was a new feature. While I haven't tried it, my guess would be to add you account to the testing enabled devices. This can be found like this:
Settings button on the left side(the one that is a gear)
Account details
Gmail accounts with testing access - add you account to this and you will probably be able to see your app on Google Play(you might have to wait a few hours for a refresh, so give it a chance
Have you published the app? Or just uploaded it?
You have enter some information and confirm publish restrictions, set the price, etc.
At the end you heve to press publish key on top right corner.
Follow this steps,
1) Upload app in alpha
2) Add any group groups, Google+ groups
3) Publish the app and again come alpha page added group, you will have url which you need to give to your tester.
Hope this help you, let me know if you have any issues.
if you mean how/where can you find the alpha version of your app? I think you could find the Opt-in URL to see and download your app.
Simple question, as i can remember there was an option at the developers console in the Play Store to make an app only visible to a set of email addresses. Or at least the app would be free for that set of emails.
So is there an option to make an app only visible to a specific set of email addresses on the Play Store?
I'm asking this because i want to test my app, therefor i have to email it to like 50 people (not a problem). But when i update the app in the "beta" stage i don't want to resend those emails, and ask the test users to update the current install. Using the Play Store updates would be more seamless and automatic.
Does anyone have experience with this situation?
Edit:
It seems that there is at the moment only one simple answer:
No, using Google Play it's not (yet) possible. But there are some alternatives out there, see accepted answer.
It would be great if Google could add this functionality to the developers console, this would allow developers to simply bring out new updates, and easily see crash rapports without having to publish the app in public.
Edit 2:
Now it is possible to Alpha and Beta test your applications! I believe since the 15 of may 2013.
https://support.google.com/googleplay/android-developer/answer/3131213?hl=nl
Google Play now has alpha and beta testing built in:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
I personally don't remember seeing the option you mentioned, specifying email addresses for private delivery and therefore, I have no experience on that matter. In fact, a quick check in the Developer Console, revealed that the option is no longer available, which I am sure you already know since you posted a question for the same.
That being said, there is a web service I am aware of (never used it personally, but is recommended by quite a few of my developer friends and colleagues).
The website is: The Beta Family. A cursory look at their website so far hasn't mentioned any fees or payments for creating an account or uploading an app for testing.
They also have the email feature you mention in the OP which they call SuperSend where you specify a set of email addresses and the app is delivered to them.
You can get more information about the same here: http://thebetafamily.com/supersend/
It may not be useful if you are looking specifically for a solution with Google Play. But if you open to alternatives, I think this looks promising.
Hope this helps.
EDIT: Their FAQ's mentions that their service is, in fact, free.
I am working on learning in-app billing but I am having a problem with the google's in-app billing example, the Dungeon one.
I have already set up the application, added my public key, and changed the API_VERSION to 1 in the makeRequestBundle().
I have already exported and signed the application and uploaded it onto Google Play and saved it as a draft with a few pictures and activated the apk. I also added both the sword_001 and potion_001 as published in-app purchases!
Next I installed the signed app onto my phone but when I try to purchase either the sword or the potion I get an Item unavailable error
The item you requested is not available for purchase.
I even tried on a different device to make sure it wasn't because developer's can't purchase their own products, and I get the same message on both devices.
What have I missed?
Check your versionCode. It can't be higher than the last published/unpublished version in any of your distribution channels (prod/beta/alpha).
In app billing seems fraught with pitfalls, but this is what I found that affected availability of items for purchase and also suitability of application:
My code for what it was worth was strongly based on the Google Android demo, but I stripped out a lot of the complexity. I have a feeling that having got it to work a better result would be produced by writing it all again from scratch.
I got the static test product ids going first.
Despite what the documentation says, it seemed to me that the purchase item(s) must be published, even when using a test account. Mine didn't work when they weren't, anyway, and I waited quite a long time to see if they would start to work as others have suggested - they still didn't.
You (I anyway) can't publish a purchase item without publishing the app, so what I did was upload and publish the app, create the purchase items, publish them (big button at the bottom of the page), then unpublish the app again. This seems to leave the items published.
The app must be signed in the usual way (I did this by exporting from Eclipse) before uploading, but what isn't so obvious is that the app you load to the mobile MUST also be signed in the same way - ie a (debug signed) version loaded to the device by Eclipse - run or debug - isn't going to work.
They also both need the same version number, I think. Not 100% sure. If so that would unfortunately kind of imply that customers with old versions installed can't purchase anything without upgrading.
When the app is uploaded to Google, it can take several hours before it becomes available and you get all the right responses for the in-app billing. I find 1-2 hours typically.
I suspect the other comments on this subject about whether you use a gmail or googlemail test account might be red herrings, but for what it is worth, my test account is gmail.
I did come across a useful little note on the internet somewhere about how to change your primary account on the mobile without having to do a hard reset (and consequently losing everything), but unfortunately I haven't managed to find it again.
What I did find though is that one can have several google accounts on the mobile, and then select the one to be used by Google Play.
Hope this helps somebody. I have to say its a pretty complicated system, with not many switten down answers, and I nearly gave up on it.
If your app are on closed alpha testing, you have to sign in with your test account to Opt-in URL; https://play.google.com/apps/testing/{your.app.namespace}
My experience on this error is:
Make sure to upload the signed APK to developer console.
Make sure to install the signed APK on your device not launch the app in the debugger.
Make sure to create a test account in your developer console.
Make sure to sign in your device with your test account.
Make sure to create in app billing in your developer console and finally activate the item from the console!!! (this is the one that got me after fully following google's tutorial)
It's no longer sufficient to just upload an unpublished draft apk to test in-app billing. What you need to do is upload an apk to the alpha or beta apk section on the Developer Console. Then, you need to publish it. If you also have a draft apk in the Production APK section, be sure to delete it before you publish. Otherwise it will be available to everyone.
Publishing an alpha or beta apk makes that apk available to only those testers that you specify/allow.
Here is Google's documentation on this:
https://support.google.com/googleplay/android-developer/answer/6062777?rd=1
Well I found a solution to my problem. I wasn't able to get Google's in app purchasing example to work but I was able to get this InApp Billing Tutorial to work using the steps I mentioned in my original post.
If nothing else this may be helpful to someone to see all of the steps that need to be done to test one of the in-app billing examples.
Also had this problem for a couple of days and searched around a lot. I found this guy who said deleting the app and then reuploading fixed his problem, and that actually worked for me aswell.
Try that, delete your app from the developer console entirely. And reuppload a new signed apk and set it up all over again
Publishing the app did the trick for me(and leaving it published (!)). I had to wait a bit for Google to update their database as well, as mentioned elsewhere, changes on Google Play are not immediate.
Anecdotal Supplement: If you have an existing app in the portal already and you want to test a signed version, but not upload it into the portal for distribution. Do the normal steps to build a signed version BUT use your latest version code that is uploaded into the portal. You will will be able to do a quick and dirty test of purchasing (you can't upload this version on the Google Play portal, but it's a means to an end for a localized test (or even as a way to allow side loaded distributed versions/flavors that use Google Play for billing legitimately.)
3:)
Check if your device have more than one account then remove other accounts and keep the account you have entered in play console then it will be solved.