I am implementing an IAP scheme for android, and I have come acrossed something really strange. I have started from the TriviaDrive sample that Google offers, I have changed the key to mine, I have signed it with the developer key, uploaded it to Developer Console, created the IAP items (managed) and activated them. The app is in draft mode.
The situation is that I can buy one item with a test account, it looks to be consumed and I received an email from Google saying that I have made a purchase. So far so good. But unfortunately, if I try again to buy the item, the same process happens again, email from Google included.
Does anybody have a clue of why this could be happening? I've check dozens of time that the products are managed, that my key is correct and they are right...I'm quite lost now.
Thank you very much in advance!
I finally found the problem. I had a line in the code in which I was consuming the item, thus making it elegible to be purchased again. It turns out that a managed product can be consumable after all.
Related
I have a problem on developing subscription plan.
Doesn't find the answer from
How to solve DF-CPA2-07 PlayMarket error?
It could work on first purchase when no plan is subscribed but fail on upgrading one plan to another. Got the error [DF-CPA2-07x8] from Google server. Clear data and cache for Google Store App doesn't work. Need some advice, thanks
This means the process took too long when doing the upgrade and timed out. It is a problem at the Google Play end. If it is happening frequently and repeatably for you then you should contact the Google Play Console support team and ask them to report it to the Google developers. They will collect some more information from you, and be able to look at exactly the request that is causing the problem. They will be interested in the exact error code, the app, and the account that was making the purchase, as well as the logs from your device.
You can contact support under the help menu in the Google Play console.
Okay, something really dumb happened to my friend.
He submitted an Android application a few weeks ago that offers In-App Purchases to the user.
Now, he needed to update the .apk to fix a bug, but he actually lost the keystore that he used to sign the application the other day (what a dumbass...). He tells me it's definitely lost. He exhausted all options to find or restore it, but without success. So, as he understands, the only way to submit the update is to actually create a new application in the Google Play Developer Console. He is so dumb, I always tell him to do backups of important files, he just won't listen (wow, really, such a blockhead...)!!!! sigh...
Luckily, he only had a handful of users who actually purchased something in his app during that time. However, I would like to know (for my friend) if there is any way to transfer the In App Purchases from the same user from the old app to the new one, so that the users who bought something in the app and now want to update it, won't get punished for his stupidity and have to purchase the same items again....
AFAIK, there is no way to do that. The only option is to refund them and ask them to buy again in the new app. I believe refunding can be done by logging in to Merchant account.
Google Play does not provide any form of content delivery. You are
responsible for delivering the digital content that you sell in your
applications. In-app products are always explicitly associated with
one and only one app. That is, one application cannot purchase an
in-app product published for another app, even if they are from the
same developer.
And BTW, Does the app have any backend? Where in he saved data of all purchases made?
I know there is a lot of questions about this out there but I've already looked at all of them! Especially this one which has a lot of other questions inside it. But I still keep getting the "the item you were attempting to purchase could not be found" message. I have no idea what I might be missing here.
I basically did everything the user of the question I've mentioned above did:
The in-app item has the status "Active".
I have entered an account other than my developer account in "testing access".
I am using a device with the primary account in the "testing access" and not the developer account.
I have double checked the spelling of my SKU.
The exact same .apk was uploaded to Developer Console and installed on the test device.
I have double checked the license key.
I have waited more than 12 hours for SKU and testing accounts to be propagated.
I've also did what he marked as the correct answer, that is publishing the app on the alpha channel (I've already tried the beta channel too) but it just won't go!
Anyone could help me please? I don't have reputation enough to make a comment so I've made another question
I found that you actually have to publish the app before you can do any testing. That is not what the Google documentation says, and was not true when I implemented the v1 version of the API many years ago. But I do know I was always getting those purchase item could not be found errors until I really published my version of the TrivialDrive app.
There are other queries on this, but none seem to provide the answer.
I am trying to implement in-app billing. Code in the real app is based on the dungeons code. I have to managed to get it all working fine on the test ids, but cannot get it to work with a real purchase id. I have:
Signed the app by exporting from eclipse.
Installed this version to the phone.
Uploaded same version to google play, saved it, activated it, but left it unpublished.
Created a managed in-app billing item.
Published that, although I notice that it does say 'item will only take on published state when app is published', no way round that as far as I can see.
Checked carefully that product ids match.
Added a gmail test account, made sure this is the primary account on the phone.
Waited several hours to make sure it gets propagated across all servers.
And all I get is 'item is unavailable for purchase'. It finds the item OK because in the background on the screen under the dialog is all the right info about it.
What is especially annoying is that the exact same billing code when built into a pure test app, does work, and I can purchase a real managed item. So I am sure the logic in the code is working. It just does not work in the real app with the real managed item.
I feel therefore that this must be some sort of fault with what I/Google have done at the developer console end, not in the app code.
Any ideas? I'm at my wits end with the whole in app billing system.
It was just time in the end.Took over two days to sort itself out.
I have implemented In-App purchase in my app. I am able to create different In-App products along with test accounts. But the problem occurs when I purchase In-App product, it shows a message "The item you were trying to purchase could not be found". But the item is existing with exact product id. Can anyone help me?
Is the purchase item marked as published? If it isn't you may get that exception.
Take a look at Google's documentation. Step 2 talks about marking items as published. You also have to ensure the application is signed with your release certificate.
try doing it without test account, it will work best luck :)