I added an Application in Google Play Market. After that i added two products and publish them. After that i purchased some products with my test account. But 2 Days later when i tried to purchase a product. Google play server not gives me any Error and also not shows Purchase window.
As I was created test account which you used to purchase the product. After several purchases the Google play blocks that account for some time for purchases. I faced that problem already, and I did R&D on that. Finaly we implemented a solution i.e create another test account and do purchase using it, as old account get blocked for purchase . After some days you can try with previous account, then it will work fine.
Related
Good day.I have implemented the in-app purchase flow in my application,added everything necessary to the console but i am failing to test it.Issue is that the android i dont know why uses the non-testing account (developer account) as on the purchase dialog it says 'The publisher can not purcahse this item' but although i have added test account to the device,switched account in the google play but i keep getting this error.Can anyone please tell me what is wrong with it?
If you want to test in-app purchase, you need to account on https://play.google.com, publish your app in alpha version. In IN-APP PRODUCTS, you add products you want, add emails you want to test (only emails in the list can test). You follow this link:
https://developer.android.com/google/play/billing/billing_testing.html
I have developed one application in android with in-app purchases feature.
First I tested my application with test purchases using android.test.purchased it works fine when I tested using test purchases.
Second I uploaded new application with different SKU like product id's
in playstore as a beta version and I tested that application using test accounts then also it is working fine and it is purchased. And I added in-app products in playstore.
But the problem is when I promote my beta test version into production it is not purchasing what I want, first it is purchasing and when I click one next time again also it is asking for purchase so every time it asking for purchase it s not proceeding to next action.
I followed this tutorial to implement in-app purchases [in-app purcahses in android
In my application I have used mHelper.onConsumeAsync(). So I removed this method when I click on the button so next time it is not consuming(means not asking for purchase second time).
So it is useful for consumable products like subscribed products(Non-Managed products).So I am not used that kind of products I used only Managed products when purchase product I am not purchasing again and these transaction will be managed by google.
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.
I have created google play test account for testing In-App billing, but the problem is that when i purchase the item and then uninstall app and then install it again on that device and test for In-App billing it gives response that the app is already purchased. So how can i remove the old record of purchasing from test account on Google Developer Console.
Any help will be appreciated.
Since your product is Managed Product by Google therefore your purchased item is already connected to your google account. The best way to get around is to use another gmail account or create a new gmail that you can use to test again.
Secondly, It's always better to test your purchase with static response i.e "android.test.purchased" in your product ID field. If everything goes fine here then try it on Alpha/Beta mode in developer console.
In Android In-app billing version 2 subscription static response is not working, This static response like android.test.purchased is working for inapp products, but the same is not working for subscriptions
1) IS there any other of testing it( we would like to do a static response testing which save our time
2) Can any please share a working code of in-app billing subscription
Testing inapp subscription billing is horrible. You can test out of your SDK for the adroid.test.purchased to make sure you are parsing responses properly. To test the subscription, add a test product to the subscription products on the developer console and publish the product. You must publish the products for this to work. Get up google groups and add test email accounts to the group. Invite the testers. THEN upload your .apk to an ALPHA and publish it. you must publish it as an alpha for the test phones and logins to find it.
Go to the link provided under the ALPHA tab to set up testers and log in from the phone using one of the test emails. Buy the inapp product to make sure all your code works. You can cancel the test product purchases in the Google Wallet and re-use the products until the code is correct. THEN set up a test subscription product. You will only be able to test the subscription once per test email. There is no way to remove the test subscription. Be sure to change the product names in your apk before you upload. Also, change the version code in the AndroidManifest, and turn off debugging.
If you try to install the app twice on a device, you may need to clear the data from these apps under settings in the phone: chrome, play store, play services, or it will continue to think you have it installed and won't download it. You must access the test .apk from a browser, NOT through the play store.
This is the most onerous testing I have ever experienced. Also, watch for errors from Google IABilling response, since the "already owned" response for a product is different for a subscription. I am still trying to figure out what the response is for the already owned subscription. Will update if I find out. This explanation is the ONLY information available anywhere that I have found, and this was weeks of trial and error. If you have more data on this, please share!!!