I have an alpha working version of my app.
I have set the alpha open.
I successfully tested the in app billing with the test account (meaning the money is not charged to the test user).
I successfully tested the purchase with static response.
When i try to test the real payment it always say "the item is not available for purchase"
The version and the signature are ok.
Can you suggest what am i missing?
BILLING_RESPONSE_RESULT_ITEM_UNAVAILABLE 4 Requested product is not available for purchase
this is the returned code but i think has nothing to do with the real problem.
where can i find more information about the error?
I don't have the reputation to comment yet, but have you tried making a purchase from a version of the app that was downloaded off of the play store instead of a version that was run from adb or android studio?
Here's someone who had a similar problem
GooglePlay: The item you requested is not available for purchase
I encountered a problem like this as well once - i.e. downloaded the app from the Play Store, with a test-account (aka no money purchase) it worked, but a real purchase with a non-test account failed.
For me the reason was that the merchant account linked to the Play Store was not set-up correctly. You might want to check that if your situation is similar.
Related
As the title says, I'm getting the error "item unavailable in your country" when trying to test purchase an in-app product. What confuses me is that a couple of days ago it was working fine. You can see in one of the screenshots I was able to successfully purchase a product. Now today I am unable to. Does anyone have any history of this happening? if so what did you do to fix it?
I had the same problem yesterday. It corrected itself after I uploaded a new version. I hadn't upgraded since late April, so I put it down to the fact that the upgrade interval was too long.
I wonder if this problem is related to the new Google Play Billing Library 5. Play Billing Library 4 is still meant to be ok, but QuerySkuDetailsAsync is now deprecated and has been replaced by QueryProductDetailsAsync. See https://developer.android.com/google/play/billing/migrate-gpblv5 and https://developer.android.com/google/play/billing/compatibility.
All my subscriptions in the Play console are showing updated May 2022 and I've not made a change to any subscription for months.
I just tested again with my app and it all appears to be ok for now.
If you have uploaded the build in the closed track, please ensure that you have accepted the test invitation from the invited email or it will show this error.
Step 1: Go to Release -> Testing -> Closed Testing
Step 2: Click on Manage Track
Step 3: Click on Testers tab
Step 4: Scroll to the bottom and you will see 2 options. Copy the link for the web and open the link in your phone or browser with the test email you want to test.
Step 5: When you open the link you will have an option to Become A Tester. Click on that and then you are good to go.
This problem occurred again today on a device that I haven't used for a while. I knew that the subscription had expired because when I queried the subscription it failed and the reported exception from Google's servers read "The subscription purchase is no longer available for query because it has been expired for too long." The subscription was purchased on May 10th. From previous testing expired subscriptions for beta testers are still returned for something close to 40 days. At that point, the beta tester then has to purchase a new subscription.
I, therefore, attempted to make a new purchase and got the "Item unavailable in your country" message. The way around that was to use the Google Play link supplied to a beta tester and then reinstall the app directly from Google Play. I was then able to successfully purchase a new subscription.
My conclusion is that Google Play has changed the procedure because I've never had to do that previously when using any of the devices I test with.
Currently also experiencing this bug in a particular game. But works fine in my other games
I'm trying to integrate Android Market in-app purchases into my app, but unfortunately coming across an annoying error every time I try to purchase a real inapp product.
I'm using Unity3D and Sommla framework for that. The surprising issue is I can purchase the inapp products just fine when I test run the app in the Unity Editor but every time I try to test it on my Mobile device I get the annoying error:
The item you requested is not available for purchase
I googled the about this error but nothing seems to work for me, I have already made sure that:
The APK is signed and uploaded to the Developer console as alpha.
Installed the App on the device through Unity Build App
Have a Test Account in my developer console
In app product is configured in the developer console and is activated
The app version number and version code are same as they are on the developer console.
Any ideas guys?
If you can purchase via test in app purchase id android.test.purchased and trying real id to get product in development build of android then don't worry. Once it gets live, this error will no longer be visible and you'd see the actual product with actual price.
I am adding some more scenarios to occur the same error:
The Phone Should have a valid Gmail account and need to configure in Settings account.
If the account is added to the Sandbox, you need to configure a valid credit card to the Gmail account. If the Gmail account has no valid credit card, the same error will come (The card won't be chargeable in Sandbox).
Im trying to get In-App Billing to work. I have followed the tutorial from http://blog.blundell-apps.com/simple-inapp-billing-payment-v3/ somewhat, and I get purchases working. Although from both my testing devices at some point it stops to work. What also stops to work at the same time is paid apps in full and Ill only see free apps.
From my developer account testing against the reserved products, i found out the reason that my account had somehow been logged out? And when logging back in it work, happy with that :)
From my testing account against the published product I got a message saying "product not availabe from merchant" or something like that. Then that account is crashed (not available to make purchases) and I cannot get market working again.
I have:
- Verified multiple accounts does not exist
- Ensured my account is still logged on to market (the case from developer account)
- Cleared google play cache
- Removed the account as testing account
- Restarted the device
Any ideas here? I could understand if my app wouldn't work due to poor coding, but what is this behaviour, diasabling the market for the account? Could google play block my account due to spam? And does 10 IAB setups or so count as spam?
Thanks in advance!
Developers cannot purchase their own products. So you can build a signed version of your apk and test it on a device who's primary account is not tied to your developer account. I had to use my wife's phone to test my IAP. Also note that you have to wait a while before your products (SKU's) will be available.
I am trying to test subscriptions in android app. I use dungeons example. I uploaded apk which is not published, but subscription items are published. I added new test account(gmail) in dev console which is not developer account. I reseted phone to factory and added test account. I installed signed apk(same version as uploaded).
When I try purchase I get "The item you have requested is not available for purchase" but I see in background item which I requested.
Some thoughts what can be problem here? Thanks
Same thing happened to me when I tested in-app billing, and there was no other way to overcome it but to actually publish the application. Once the application had "replicated" to Google servers (which took several hours, during which I got yet another obscure error message when trying to purchase anything), buying subscriptions worked fine.
use this link and refer table 1. I also faced this problem.http://developer.android.com/guide/google/play/billing/billing_testing.html#billing-testing-static
Have a look at that table than u will get that whats going wrong in your table.
I had the same problem. After changing the APK state from unpublished to Activate (in APK files tab) and waiting for 1 hour or so, the product ID could be purchased.
Make sure to upload the signed APK to developer console.
Make sure to install the signed APK on your device not launch the app in the debugger.
Make sure to create a test account in your developer console.
Make sure to sign in your device with your test account.
Make sure to create in app billing in your developer console and finally activate the item from the console!!! (this is the one that got me after fully following google's tutorial)
I'm implementing in-app billing in Android and it's giving me headaches.
When I try to buy my products from the in-app store, bang: "Item unavailable",
but if I try the android_test_purchased everything goes fine.
I made a list with 'all' the possible causes for this problem and checked each one.
Here is the list:
in Security.java, the public key should be same as the one in the Android Market account
the version of the Market application in the Device should be 2.3.4 or higher
the device you use for testing must run a standard version of the Android 1.6 or later
the application being tested must be uploaded as draft, in the Android market, and must be signed
the application installed in the device must be the same as the one that was uploaded as draft to the market
the device must have a something#gmail.com account as its primary account and this account should be defined as a test account in the Android market
the products for in-app billing in the Android market must have the same IDs as the ones displayed in the application
the in-app products in the Android market must be published
Any suggestion and modification to this list is well appreciated.
Thanks
one more point I like to mention is
The account u are using for test purchases must b mentioned as a test account in your market account
I've ran into same issue. Solution was to wait, it take several hours, perhaps one day, until published items in unpublished app become "online".
I might have the same problem. There seems to be a known issue that test accounts created after August 1st is not working.
See Known Purchasing issues from Help pages
No mention anywhere when this is resolved though..