in-app-billing

I am having trouble figuring out how to verify Androind In-app Billing purchases with my Ruby on Rails server. http://developer.android.com/guide/market/billing/billing_integrate.html I think that Android gives a Security.java that has some sort of method to verify on physical device. From my research it seems like either (1) I need to figure out how to use this Security.java class with my Ruby on Rails server or (2) I need to port Security.java to Ruby. Is this correct? Does anyone know another way to verify the receipt? I just figured this out. Basically the way it works is that when a

edit 4/15: Catching nullpointer in IabHelper appears to have stopped this problem. I am no longer seeing the exceptions being thrown, I'm going to accept this as an answer. edit 4/04: A little bit of a deeper dive. There are try catch blocks that handle RemoteExceptions and JSONExceptions for the queryPurchases method, but no NullPointerException handling. What I am going to try is include NullPointer Exception handling so IabHelper looks like this when trying to querySkuDetails: catch (NullPointerException e) { throw new IabException(IABHELPER_UNKNOWN_ERROR, "NullPointer while refreshing

Whenever starting payment service everything is ok but in activity result got Error on activity result RESULT_OK = 0 and resultCode =-1 as expect in sample example but i don't know where is going to wrong.. if (Navigator.REQUEST_PASSPORT_PURCHASE == requestCode) { if (RESULT_OK == resultCode) { dealWithSuccessfulPurchase(); } else { dealWithFailedPurchase(); } } there is control goes in else statment .. check my below code: @Override protected void onActivityResult(int requestCode, int resultCode, Intent data) { Log.d(TAG, "onActivityResult(" + requestCode + "," + resultCode + "," + data); if

Does InApp billing (V2 or V3) works for a user who uses several accounts and makes the purchase with an account that isn't the primary one? PD: Some explanation required, no simple Yes/No In App Billing support multiple accounts reported as a bug in code.google , have a look at it According to Mr.Sergej (posted in G+ android dev community) in-app products purchased with the first account won't be active anymore while using multiple user accounts!. InApp billing just charges the user and tells your app whether it was successful or not. It is up to you to figure out how to give the user what

I'm always getting "RESULT_DEVELOPER_ERROR = 5 - invalid arguments provided to the API", when trying to consume a purchase with String purchaseToken = "inapp:" + getPackageName() + ":" + productId; int response = 0; try { response = mService.consumePurchase(3, getPackageName(), purchaseToken); } catch (RemoteException e) { // TODO Auto-generated catch block e.printStackTrace(); } For that reason, I can always only make a purchase once. However, I need to be able to make the purchase much more often. I've been trying to fix this problem for 2 days now, no success. :/ Making and consuming

With version 3 of the Billing API, Google has removed the distinction between consumable and non-consumable products . Both have been combined into a new type called "managed" and behave somewhat like a hybrid: Your app needs to actively call a method to "consume" the items. If that is never done for a set of skus, those items basically behave as if they were non-consumable. The documentation describes the intended purchase flow as follows: Launch a purchase flow with a getBuyIntent call. Get a response Bundle from Google Play indicating if the purchase completed successfully. If the purchase