Can i test my in-purchase with with subscriptions in draft. App is already live with one subscription. I need to test new subscriptions added in play store. but they are in draft and I am not able to fetch their sku details. Can someone help. on note from my side is that I am able to complete purchase for other plans which are live in market.
How can I get skudetaills? Do I need to make subscriptions active?
Related
I want to enable in-app purchases in my flutter app, but currently I'm not getting the product list from the google play store. For the first step, I want to implement in-app purchases for android.
From my understanding, a submitted app package is necessary, so I uploaded a valid and signed app package in the closed testing track (not rolled out yet (!)). After that, I was able to create subscriptions.
But I cannot find the subscriptions in the app. What have to be done to make the products/subscriptions visible in the debugger? To actually buy subscriptions, I need the licensing key. But for requesting the available products/subscriptions the key is not necessary, or?
I have just developed and deployed an app to the Google Play Store.
As you can see, it is an alpha release. I have read that alpha releases can have their in-app purchases tested, without the tester having to incur a charge.
I have set up closed testing and assigned myself as a tester. I then download the app through the Play Store on my devise. I then attempt to test the in-app purchases, but I get the following:
As you can see, I cannot make the purchase as I don't have sufficient funds.
Question
How do you test in-app purchases so you are not charged?
Thank you
Adding a user to the alpha does change his purchases to be a mock purchase.
In order to test purchases you need to add your email to the list of accounts with testing access:
Go to Google play console
Settings -> Account Details -> License Testing
Add the your email to the list. Make sure that the you login to the play store with the same email.
Make sure to pick RESONSE_NORMALLY in the 'License Test Response'. Later on you can test other types of responses from the store.
Once you have that setup, you can make purchases from that account. When you purchase you will get a message from the play store saying that this is a test purchase and that your account will not be charged.
This is how it looks like -
For more information see https://developer.android.com/google/play/billing/billing_testing.html
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!!!
I am trying to test the new subscriptions in Google Play but the service returns "Item not found".
I've used the identifier "android.test.purchased" to test.
With this identifier I can test perfectly the normal in-app product, but whith subscription it doesn't work.
In the Google Play Console I added a subscription, and it is published.
Do I have to use the real subscription identifier and pay for testing?
Thank you
Even I have been looking for this , and am guessing that you may have already solved your problem.But this might help others
Even I have been unable to find any documentation about test product-ids for subscription however Testing In-App billing suggests only use of 4 reserved static product ids. This makes me infer that there is no test-id for subscription.
Hope this helps
yes,you will have to use real subscription and pay (you can cancel later).
there's no test for subscription.
notice that you will have to send in your request
api version=2 and product type should be "subs".
Google Play has already implemented a sandbox to test subscriptions and issue purchases. You need to publish your app in beta and after a few hours of doing that the test users(added in Google Play dev console) can make test purchases(these are not charged) in your app. They can even make subscription test purchases. A test subscription automatically renews every day(until canceled from Google Play) irrespective of the subscription duration.
Although, please note that the test user(Google account) must have a valid credit card added to the Google Wallet account in order to make test purchases(which are not charged). While making the purchase, the purchase confirmation dialog clearly mentions that this is a test purchase and you will not be charged.