in-app-billing

I have an android app with renewable monthly subscriptions. In this app I want to notify user some info when his subcription continues in next month. As I can see renewals in merchant center(orderId ends with eg. ..0, ..1), but when querying the inventory my purchase orderId is same as befor eq. { "orderId": "GPA.XXXX-YYYY-XXXX-ZZZZZ", "packageName": "my.packageName", "productId": "my.sku", "purchaseTime": 1456398623654, "purchaseState": 0, "developerPayload": "mypayload", "purchaseToken": "token", "autoRenewing": true } What bothers me more is that purchaseTime also doesn't change. So my

The Android docs say that its meant for "supplemental information about an order" but at the same time it also says not to use this to send "actual data or content". So what is the purpose of this "developer payload"? Why does this feature exist? Can you describe a real-world practical example of how I can use it in my own In-app Billing implementation? Bill The Ape As aromero mentioned the developer payload field is limited in size. This is why the docs recommend not to use this key to send data or content. What you do instead is save the content to a database somewhere (e.g. on the user's

I'm trying to test in-app billing using my own sku/product ID "upgrade_to_premium". As I have seen recommended here, I am using the Dungeons sample app. I've added a "new CatalogEntry("upgrade_to_premium", R.string.upgrade_to_premium, Managed.MANAGED)" to the CatalogEntry[] array in Dungeons.java. In Const.java, DEBUG is set to TRUE. I have uploaded my release-signed .apk to my Developer Console and activated it, and installed this same .apk to my device with adb. I have entered an in-app product of the same name in the Dev Console, and published it. I am logged into my phone not with my

I would like to know what the maximum number of items that can be placed in In App billing for both Android and iphone. I seem to remember reading around 3000 but I cannot find the reference. Also if 3000 is the maximum what are the legitimate way to get around this. My app will sell content and I thought a possible way around the problem would be to have a central app that shows the content, then a number of different libraries where you can purchase the content. Would that be a viable work around? I can only answer the Apple part of your question. I just spoke with them 2 weeks ago, because

Ok so I have been trying to fix this for days, and I'm not coming here looking for someone to do my work for me as I have been troubleshooting and fixed every single error message in the LogCat. I am developing an Android game using Andengine (this might be part of the problem so being familiar with it could help). I'm not doing anything too fancy, my game activities are all single scene and don't have any Physics or anything like that, just a bunch of sprites and textures. I also used Andengine for all of the other activities in my game because I find it to be a very easy way to set up