I need to test my in-app Purchase app before uploading it in Google Play store.
I have created the Beta testing Group with my mail account. But still I am getting error "App not available for this account".
Please share your ideas for this.
It may shown because you have not added account in Gmail accounts with testing access. You can add following way,
Open developer account for publishing app.
Go to Setting, you can find left hand side under All Applications
Scroll down in Setting, You can find LICENCE TESTING and add your accounts for you want to do testing.
I hope it will help you.
According to the details of your question, You should check the following conditions.
1.The gmail account with which you want to test the application should join the beta testing group that you have created.
2.The device from which the application will be tested has to be logged in with the test account - the one that has joined your beta testing group.
3.The apk that you have uploaded to the developer console must be published.
4.Note that it may take 3 to 4 hours after you publish your app to get recognized by google.
Related
I am trying to test google play services features in an app, without publishing the app.
I went through the below link to do that.
https://developers.google.com/games/services/console/enabling
This process worked earlier but i think it has changed now, as i am getting the following error even after checking all the steps mentioned in the link above.
"The application is incorrectly configured. Check that the package name and signing certificate match the client ID created in Developer Console. Also, if the application is not yet published, check that the account you are trying to sign in with is listed as a tester account. See logs for more information."
Does anyone know if there has been any change in the process or if i am missing out something? Thanks.
You need to publish the app before it becomes available for testing.
If you publish the app and it is only in the "alpha testing" section then it is NOT available to general public; it is only available to activated testers in the alpha section.
EDIT: One additional note: "normal" uses 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).
You do not need to publish an app for testing. From the error it seems that the users/testers who want to test are not white listed. Quoting from the official documentation.
If your game is in an unpublished state, you must whitelist the user accounts that you want to grant access for testing. Otherwise, your testers will encounter OAuth and 404 errors when attempting to access the Google Play games services endpoints. Also remember to add yourself as a tester, or the Play Games SDK will not work for your user account
Hope this Helps!!
When I tried to buy all of items, then it returns the message like bellow
"The item you requested is not available for purchase."
And logcat logs.
09-04 10:06:25.374: D/Finsky(7185): 1 PurchaseFragment.handleError:
Error: PurchaseError{type=3 subtype=4} 09-04 10:06:25.374:
D/Finsky(7185): 1 PurchaseFragment.fail: Purchase failed:
PurchaseError{type=3 subtype=4}
I guess, purchase error code type 3 is billing api problem
BILLING_RESPONSE_RESULT_BILLING_UNAVAILABLE 3 Billing API version is
not supported for the type requested
But... It is a live app in GooglePlayStore and I could buy an item yesterday.
And also it seems that most user can buy items. So I think the hint is subtype=4. But I can't find information about subtypes.
FYI, The application region locked in my country. Is it the problem? But I can't find Google's announcement about it.
I have the same error , and fix the problem in this way :
In the APK section . Now tester email must be listed as testers in either Alpha or Beta Testing .
After add a tester list . the tester need to open the 'Join Test' url , after join the test , I can test the purchase .
It looks like Google changed their IAP policies again and now users must be listed as testers in either Alpha or Beta Testing. From there you must opt-in (log in to that Google account and go to the URL for your app in the Google Developer Console). I ran into the same issue and that was their recommendation.
Since our update things have changed a bit. This account will need to make sure and opt-in to the new testing-link.
Just confirmed that this fixed the issue. You must configure Alpha/Beta testers for each app you have in the developer console in order for those users to be able to make test purchases. Hope that helps!
I have encountered this error response when I published a new alpha/beta version of an app to the developer console, but it hasn't finished processing yet.
Try again in an hour or so - make sure you have opted in to be an alpha/beta tester and that you can see the appropriate alpha/beta version of the app in the Play Store and it should work.
In addition to user1454444, make sure you don't have the publisher account on the device either - It was always the case that the publisher account couldn't buy IAPs which meant you couldn't have the main account on the device to be the publisher account, if you were testing.
I have recently (like literally over the last weekend) discovered that even having the publisher account on at all - i.e. your main account is not the publisher, but the publisher account is on the device - this will cause a fail in the buying process.
I suffered with this issue but it solved very simply.
The real problem was "You cannot try billing test with developer account", even that was invited account from project owner. Only, none associated account can be tested for purchasement.
Here is another checklist I had tried.
Is Registered in Gameservice -> Test -> tester
Is Registered in Alpha or beta tester at
AppVersion->Alpha/Beta Management->Tester
Are there No developer account in chrome, g-mail, playstore, googlePlay? (Every developer account must be cleaned)
Is App published? (at lest as close alpha/beta)
Did you install app with invitation url?
Check base64 key, packagename.
Is item activated?
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
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:
I am very confused about this, both from the developer site and other similar questions.
I am trying to use V3 in-app billing. Seems to work with the static responses. Want to move on to testing with test purchases using license test accounts.
Basically - it is not working.
A signed app has been uploaded to the developer site (over 6 hours ago), and the app installed on the device, whilst not being signed with the same release key (it's a debug build and key), should work because Android Developers says "you only need to upload your application as a draft application. However, you must sign your application with your release key before you upload it as a draft application. Also, the version number of the uploaded application must match the version number of the application you load to your device for testing". Ie the code on the device apparently doesn't need the same key providing versionCode matches.
My developer console login is - say - a#googlemail.com, and I have a license test address registered (on the developer console) of b#gmail.com. The primary account on my phone is also a#googlemail.com. However I do have a secondary account on there of b#gmail.com. I do NOT want to have to reset my phone and change its one and only account to b#gmail.com.
Android Developers says "The only way to change the primary account on a device is to do a factory reset, making sure you log on with your primary account first" which seems to imply I might have to. It also then says "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" which partially contradicts the first statement. Most of the text on the site appears to apply to pre-V3 code, OS 1.4 etc, so I am not sure how relevant it is.
I notice that Google Play allows me to select the account to use, and both the above show up in the list. Therefore, if I select that second (test) account in Google Play, should that be not sufficient to start testing with that test account?
What actually happens is, whatever account I have selected in Google Play, on starting a purchase I get a message "this version of the application is not configured for billing through Google Play".
Is this because I really do have reset the device and make the primary account b#gmail.com, or because of something else, possibly in the code?
I have some more information now, together with the answer above:
Once I loaded the device with the release signed key the message on a purchase attempt changed to "the publisher cannot purchase own item".
I tried logging in to Google Play with both my accounts and it made no difference. When logged in with the test account I also tried to find the app in the play store. Didn't show up even to the test account (draft app). (I hoped the test account could download it even as draft and therefore following the rules above about multiple accounts I could test purchase with the test account, but no).
Therefore I conclude:
Can only test on a device with an app signed with the same key as the one uploaded to the play store - whatever Android Developers might say.
The ONLY account that can test purchases on a device is the first set (primary) account.
Best therefore to have a completely new account as one's Developer Console account (bit late now).
Would be happy to hear if anyone can contradict the above.
Sign the app you upload to the device with a release key. As far as I know you can't test in-app billing without signing it properly. Actually, last week I tried it as written above and it works.
Hope it helps.
You can have multiple accounts on your devices -- as many as you want. But while testing the app, make sure you don't install it by the app Play Store on your device. Instead, go to Google Chrome, browse to its page on Google Play, and install the app from there. There's a button Install (or Installed).
I guess if you already install the app from account A, then the Android app Play Store will use that account to install next version (or reinstall current version) -- even though you're signed in as another account, like B for example.
However the Google Chrome will just install the app via the current signed in account. This could be a bug and it would be fixed some day. But it's working right now -- when I'm typing this answer. Android team is well known of being lazy for delivering fixes. I hope this "bug" will never be fixed :-)