I implemented google play IAB sdk but when I run the application I got the following message:
Authentication is Required. You need to sign into your Google Account.
Although I published the application on Developers Console and also I double check the ProductID.
I guess you are testing your app directly from Android studio, you have to create a closed beta, add your email to testers and publish.
Use only signed APK to test inapp purchase with same version code and version name as you have in published APK on google console
Also add your email to tester
In addition to #Tinco De Simone's answer, maybe you are trying to access wrong item id from the console. From this thread, "In the developer console subscription item had id "premium" and I've tried to access "premium_version" item". Double check if the itemID fits with id that you request in your app.
Also be noted that it might take up to 6-8 hours before a newly created in-app product is available.
You may also check this related SO quesiton: Android IAB. Error - Authentication is required. You need to sign into your Google Account
This message indicates that, may be you are not logged in with any Google account in your testing device, as Google pay always requires a Google account to purchase anything from play-store.
Related
I'm not testing my in app purchase !
I have download my app from google play store and I still can't buy any of my In App purchase within the application.
I have the following error : "The publisher cannot purchase the item".
All my In App purchase are also valid and active.
I'm using the same google account than in my google play developer console.
I have read on google that it's normal that developer can't buy it's own items in testing mode (alpha or beta) but here i'm using the official version and I still can't do it !! (It's my first android application)
What did I do wrong ?
Thanks,
if you have the same account configured on the device (the one which you are using for developer console) make sure it is removed. Google Play will allow switching between all google accounts added on device. Also, before removing try switching directly in google play first to an account that is not your developer account and then do the purchase. If that doesn't work you'll probably need to remove the developer account for the device if you want to make a purchase fro your own app.
Using in app purchase in my application. I have double checked the products are listed at playstore and in active states. plus the application is published but in beta testing. product ids using in my code is very same as in playstore. I'm testing the signed apk on phone.
Problem: whenever i click the button and try to get product it endup like this.
please help. thanks
Step you need to follow, once launches an inapp products in your application.
You have latest In-app Billing Version configured in application
Apk is in published state but in beta testing or any other testing
List the products with unique ids at play store panel
Change the state of products to active state
Product ids are same in source code as well in play store (double check)
You have signed apk installed in phone
versionCode of published apk & testing apk must be same
you have added a tester at play store under same apk
You need to test inapp from very same email, you have added at google play store (as tester)
once i followed all steps this error is gone. In my case it is because of tester's email :)
You have to use a different (test) account than the one you're signed in to the developer console with, and add it in the developer console.
Edit: see here: the item you requested is not available for purchase
I think, you might miss something but to get the missing part, you must share your code of InApp Billing section. By the way, you can also use the library project from https://github.com/anjlab/android-inapp-billing-v3.
Possibly a caching problem with Google Play services. Clear out the cache and try again.
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 integrated Google IAP Billing to an Android application.
I published my application in Alpha version on Google Play Store. I copied the public key that I added in my project on Android Studio. So, I use the good Public API Key with my IabHelper instance.
I signed an APK that I use on a device with an unique account that is different from my developer account. This account is added in the license testing emails field on the Settings part of Google Play Developer Console.
I also checked the SKU ID of the item I want to purchase is the same on my application and on the application signed.
When I launch the buy process, I get a dialog with Please sign in to your google account error. But, I am already connected because I can go on Play Store application and download apps. I also tried to clear cache data for Play Store app and Google Play Services but nothing works for me.
I must mention that on the manage list of alpha testers, I have created a google+ community like asked but there is no link to send to my alpha-testers to opt-in.
Someone has an idea about the problem ? And the solution to solve it ?
The alpha tester has to satisfy these two conditions:
joined the alpha testing community
opted-in for alpha tests
Firs you have to invite the tester to the alpha testing community. Second the alpha tester have to opt-in using this URL: https://play.google.com/apps/testing/your.package.name
It just takes time. Give it couple of hours and it will work.
Also make sure that the file you are running on your phone is signed with the sane certificate that is uploaded on google play (not debug file)
I have an error
Authentication requied. You need to sign in google play account.
while testing in-app billing on my device with testing account.
I have implemented in-app billing v3 and i have uploaded signed apk in developer console as draft apk and running higher version signed apk in my device.
You need to login into Play with the same account which is added as Test Account into developer account.
From Testing Your In-app Billing Application
5 . Login to the test device by using a tester account. Test your In-app Billing application by purchasing a few items, and fix any issues that you encounter. Remember to refund the purchases if you don’t want your testers to be actually charged!
As you said you logged in with the same user id, then problem might be Getting “Authentication is required” when trying to access the market
It might be a temporary error.
I just implemented the v3 billing API in one of my apps and got the same error message. I followed the TrivialDrive example and uploaded my app for testing. Last night it worked fine, but today when trying to test a purchase I got the same error message you did. I then closed the error message and retried the purchase and it was working again? It might be my implementation of Billing that is incorrect or there might be a bug in the Google example code.
I'm going to continue testing before releasing my app but I'll be interested to hear if you find a solution for your problem.
I had this same problem on my Android tablet and though I kept going into my settings to reset the new password, the same message kept coming up. Finally, I found that I needed to open the 'warning message' that was being sent to me. Only then did it 'take' the new password and allow me to use Google Play.
This problem could occur because you don`t have added the product that you are searching with the same ID added to Google Play.
Go to In-app Products menu and check the product ID or add any one.