Had the same problem. I contacted as well and got this response from Google Thank you for contacting Google Play Developer Support and reporting the behavior you’re seeing with in-app billing. We recently made some changes to our systems and we are now requiring an app to be published before testing. We are currently recommending … Read more
This indeed a know security issue from Google side, so I am going to suggest a workaround. Along with promo code provide the users with server id generated by your server, when getting a promo purchase validate the server id and accept the purchase just once. When using from market send the id with referrer. … Read more
I have the same issue previously. Go to your google developer console and make sure your app is PUBLISHED to any version(alpha, beta or prod). Then, the In app purchase will work 🙂
As I mentioned earlier in a comment you are comparing a String to a List object, but as chitgoks said it is ArrayList<String> and not List<String> as i assumed. I’m not sure if you would ever get more than one sku-string (since you probably don’t order multiple things at the same time?) but either look … Read more
Yes, there is a company called Stripe that offers an API helps do the in app billing without the need to use the Google in app billing. EDIT : For the legal aspect of this, it depends on what you are selling , check this from google play policy. App purchases: Developers charging for apps … Read more
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 … Read more
This has changed as of today! There is now an example on the Android Developer site here: https://developer.android.com/google/play/billing/billing_overview
After having waited for about 12 hours and having tried everything suggested here, I was still facing the same issue. What did the trick for me was the following adb command: adb shell pm clear com.android.vending
I had the same problem and explicitly setting the package solved it. Similar to Aleksey’s answer, but simpler: Intent intent = new Intent(“com.android.vending.billing.InAppBillingService.BIND”); // This is the key line that fixed everything for me intent.setPackage(“com.android.vending”); getContext().bindService(intent, serviceConnection, Context.BIND_AUTO_CREATE);
This issue was opened on the google’s android-play-billing samples repo. Looks like it was ignored for a long time and was eventually closed with this comment. In short, they have following suggestions. We reviewed our guidelines and internal APIs, and since the developerPayload is not supported across all features on In-App Billing API (including promocodes), … Read more