in-app-billing

I have followed to following great tutorial at : http://blog.blundell-apps.com/simple-inapp-billing-payment/ I have done everything the tutorial says and have read everything 3 times over again but still i am not receiving a signature in the intent.getStringExtra(INAPP_SIGNATURE) in onReceive() : BillingReceiver.java which makes my app crash because the app cant compare signatures to verify if the purchase is done correctly. This is how my BillingReceiver looks like: public class BillingReceiver extends BroadcastReceiver { private static final String TAG = "BillingService"; @Override public

Today I published my app, and when my friend tried to buy the in-app content the market says: "Your request could not be processed. please try again". A few clarifications: The app was published more than 10 hours ago, and is visible in the google play store. The testing with google static codes DID work all the time The buying account is NOT the publisher account Most of the code is copied as is from google's in-app billing example The in-app product IS shown correctly when trying to buy. The buyer has a valid credit card Thanks! Couple of things you have to consider. Check the public key

I folloed this tutorial to implement in-app in my application: http://blog.blundell-apps.com/simple-inapp-billing-payment/ The user can now purchase my item (com.myitem) with in-app system. After that, I set in a Shared Preference that the user has been purchased the item. The problem is if the user uninstalla and reinstall the app. So the question is: how can I check if the user has been already purchased the item? I know that I should use restore BillingHelper.restoreTransactionInformation(...) on RESTORE_TRANSACTION...but where, and how? I checked Dungeon example, but it seems to hard and

I've very confused on Android's in-appl billing in regard to RESTORE_TRANSACTIONS. I have this snippet for making a donation within my app: BillingHelper.requestPurchase(mContext, "donation"); It works great, no issues there. The problem is here, when the purchase is completed I set a boolean value: if (BillingHelper.latestPurchase.isPurchased()) { DONATE_VERSION = true; } The app works as intended after this, unless the user uninstalls the app. I store the DONATE_VERSION inside shared preferences. Storing the purchase information in a personal database on the internet is not an option. When

Now I managed to sign the apk (using Eclipse Android Tools) and adb install .. to the device for testing. But this removed the debug function, e.g. "step over" which make problem tracing much more difficult. Is it possible to debug the inapp billing using Eclipse? When you go through the in app billing documentation, you kinda realize that it can take substantial amount of time to understand this complex piece of technology. Most developers feel the need for a working HelloWorld, and then later play around with the builds. I have uploaded 2 projects The android sample project. You can download

I have two android apps (app1 and app2), both of them are free but app2 contains an in-app-purchase upgrade. Now I'm going to merge those two apps into the app1 (the one without the in-app-purchase). My questions are: How can I preserve the purchase that was already consumed in app2 so everyone who bought it will enjoy the upgrade on the combined app? I known I can share preferences, but I don't want to user to keep having both apps. Let's say a user that purchased the in-app-purchase upgrade on app2 tries to install the new combined app1 into another device - how can I restore his purchase

I am using the Android In App BIlling v3 library, and when I call bp.subscribe(Activity, subscriptionID) I get the Google Play purchase window, but the biling period is always 'per day', and the trial period is always '1 day'. I have configured my subscription to have: Billing Period: Yearly Free Trial Period: 15 days Default Price: $12 Using the above configuration, my App shows the purchase details as: 1 day trial $12.00 / day Library documentation says nothing. Tried to Google it, can't find anything.. Am I the only one getting this?? Thanks. This is a normal response. I guess you're