I want to test In app purchase in my application and I have few questions about that.
How long should I wait (few hours, fewa days)until I get Google Play link into my application for my testers?
( I mean this link in: Google Play Developers console -> All application -> APK -> Bta Testing -> Manage list of testers )
If I change my APK 'Upload new APK to Beta' this waiting process for link will start over again or can I use the same link for test?
Am I need to publish my app first before I get this link ? I mean my app is beta so it will be available only for my testers but am I need to publish it in 'Game Services' tab.
I uploaded my app yesterday into my phone via USB cable. When I try to test 'In app purchase' I got information:
'Conection Responce: 0 Setup succesful ( responce: 0:OK). '
Then typical window of Google Play opened but I got this information:
'Authentication is required. You need to sign into your Google Account.'
But I was using google account in my phone.
Do you think I did something wrong in my code of application or because I tried test it in application that I uloaded via USB cable instead install it from Google Play site?
Ps. I'm using Samsung Galaxy S6
Thanks.
There are two places where you need to publish something for an app that uses Google Play Games Services to make it available to beta testers.
Under the "All Applications" section (Android icon in the left frame), select your app, then go to the "APK" subsection to publish it for beta testing.
Under the "Game Services" section (game controller icon in the left frame), select your app, then select "Publishing" to make Google Play Games Services available to the users of your app.
Both of these steps will require you to fill in additional information in other sections as prerequisites for publishing.
After publishing in either of these sections it will take a few hours for publishing to take effect. When you publish an app for the first time you will get the link to your published app only once the publishing step has completed. The link is available from the "APK" subsection that I referenced above. The link will remain unchanged when you re-publish the app. Your testers will receive the latest available published version of your app when they follow the link. Re-publishing can take a few hours as well, so your testers would see the old version until that's done.
A user of the app needs to sign into Google Play Games Services as an additional step even when they are already signed into their Google account on the phone.
Hope this helps.
Related
I thought I need just this link https://play.google.com/store/apps/details?id=com.here.myapp.name to download an app from Play Store, but when I click on it from tester account (which in tester list) I can only see
The link of testing will be https://play.google.com/apps/testing/packagename and you can find that in Alpha/Beta publish tab.
https://play.google.com/apps/publish --> Select app --> Release Management --> App Release --> Alpha/Beta --> Manage --> Opt-in URL (URL for testing)
Updated to add tester (Close test)
Add testers
On the left menu, select Settings Settings > Manage testers > Create
a list.
Type a name to identify your list of testers. You can use the same list for future tests on any of your apps.
Add email addresses and create list.
On the left menu,select Release management > App releases.
Next, to the closed track, select Manage.
Next to "Choose a testing method," select Closed Testing.
In the "Users" section, check the box next to the list you want to use.
List of will be notified and selected user can accept the invitation and test the app.
Here's how I found it (with help from Scar Coder's answer)
Log into the Google Play Console and select the app from the list, then click the App releases option in the left sidebar, then click the 'Manage' button for your internal test release:
Expand the 'Manage testers area'
Copy the Opt-in URL:
For the new Google Play Console version
Open your app → Release → Testing → Internal testing
Tap on Testers → Scroll down and you will see How testers join your test at the bottom.
After that testers should accept the inventation, install app from Google Play and check the updates
You just might have to wait...
The initial release time of up to 48hrs is what confused me, and is not well communicated on the Play Console:
Searched for "android Available to internal testers", as Play Console stated exactly this, without the link providing an app (see original question).
App should come to the published status before the Opt-in URL is enabled. You can get your app status in the small '?' symbol or in the drop down box location above the page. Google takes some time to review the app before publish after you submitted it.
On the Play Console, there is an opt-in url that needs to be sent to the internal testers before they can be able to download the app
We had to test migration from older app versions to the one under development.
Unfortunately the link to the older version:
https://play.google.com/apps/test/<path.to.my.app>/<version code>
did not install the old version but the most recent version from the store. Even though the account was registered as "Tester" in "Internal Testing" in the Google Play Console and the developer feature "Internal app sharing" was turned on in the Playstore settings on the tester smartphone.
My solution was to clear the cache of the Google Playstore app.
Then, I had to become a developer in the Playstore again (by tapping "Settings / About / Play Store Version" several times) in order to activate "Settings/General/Internal app sharing" again.
Afterwards, clicking the link worked fine. And I got the longed-for message "This version of this app () may be old. Turn off auto-update for this app to keep it from getting updated." and could perform my tests.
https://play.google.com/apps/publish --> Select app --> Testing(in Release Part) --> Internal testing --> Testers and scroll Down and in How testers join your part take link of your app by clicking copy link part
You should visit the link on an Android device
As per the new Google Play console, you can share your app to internal testers by visiting internal app sharing upload page, Upload a new appBundle and share the link.
You can manage your internal testers under internal testing in the play console.
With internal app sharing, you can quickly share an app bundle or APK with your internal team and testers by uploading an app bundle or APK on the internal app sharing upload page and generating a link. When sharing your app this way, you can restrict access to email lists only or allow anyone whom you share the link with to download.
Source
I created an Open Track Beta release a few days ago for the first time, which has shows up as published since yesterday on Google Play Console. However if I click the 'View on Google Play' button it returns 'Not Found' and when I follow the opt-in link, I get an error that it isn't available even though I'm logged in as the creator of the app:
I do have the option of releasing it to production, which I assume would work, but would prefer to have a working testing release first.
You need to add yourself as a tester, to test the app. So open beta channel click the Manage Testers and add the mail that you use as google play account at your phone.
But I suggest you use internal test channel for this. Beta is mostly used for the apps already released and it is open testing.
So open internal test channel, add your apk and add yourself as a tester by clicking Manage Testers and adding your email (the mail you use as google play store account at your phone), share yourself the opt-link which you got from internal test instead of beta.
Then you will have early access, so you can download it from play store easily
I have integrated inApp purchase in my app and it functioning perfectly if i download app from play store. The problem is, when i install release apk directly in the device then it is not working and it's show below error,
the version of the application is not configured for billing
Make sure follow these steps to test
1) You've created an apk and you've published it to the Google Play Developer Console in Alpha, Beta or Production.
2) The app in Google Play Developer Console is NOT in Draft mode, but in Published (you'll need to make all the small circles with the check icon in them on the left side of the screen green before being able to publish).
3) You've set another test account than the one that's "attached" to the Google Play Developer Console.
4) The apk that you're using to test the purchase has the same version code, version name, and most importantly it's signed with the same keystore as the apk that you've published in the store.
5) You wait a couple of hours between when you change something in the dashboard in order for the changes to propagate. It takes a couple of hours to do so.
6) Make sure the SKU value is a valid SKU/product name (compare it with the one you've entered in the Google Play Developer Console).
7) You try to purchase an already purchased item. Get the purchased items and display them in the log to see if so. If so, then consume that product or refund the money to your test account. Note: you'll need to wait for the refund to propagate. It takes a couple of hours.
8) Make sure your in-app products are active.
For Alpha/Beta distributions, make sure you're signed into google (in your browser) with the test account and you open this link (marked with the red) and you approve to become a tester.
9) If you're using flavors to build APKs targeting different CPUs and you build for arm, armv7 and x86 and you upload them all to the store, remember to use one of them to test the in-app purchases. If you use a "universal" build which contains all the cpu libraries (basically another build than what's on the store) it won't work.
I need to test some features of my app like the "In App Billing" service so I published it in an Alpha version in Google Play, I filled all the required fields, I added the testers Gmail account, the app is signed and its version is higher than the Beta/Production version.
Since yesterday in the Alpha section of the Google Play Console I can see the app as published, but when I go to the Play Store the app doesn't appear, trying to get it from the provided link it says that the app isn't available because it has not been published or I can't access to it with my account.
I have verified the accounts signed up in the console and all is right, am I forgotting any step? Did I do anything wrong? Any help would be really appreciated, there is more than one day since the app is published and I cannot test it.
Thank you in advance
alpha applications are directly not accessible in play store you have to get link from developer account, where your apk is published there is link as manage testers click on that you will get link and only user who is member of that group can access it through registered email link will look like : https://play.google.com/apps/testing/uk.co.xxxxx.xxxxx)
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
For those of you who were installing Android TV app and had the same error as OP. Open your test link
https://play.google.com/apps/testing/{package}
on a desktop computer with account logged in on tv. Then you will be asked to participate in tests, and after acception you will be redirected to your alpha google play website. From here (on desktop pc) you can install it on your TV.
We missed the "Choose a testing method" step inside the APK menu option, thank you very much
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