[android-developers] Re: In-app billing error "Authentication is required"

[Gaurav Mandlik]

>
> hi R2D2
>

I have the same issue, i have tested  as *android.test.purchased*  the 
working fine, but at the time of change my SKU ID it will display error 
like as a say.

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/fb79fb52-ff4f-4b51-955c-4a275f92983b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Re: In-app billing upgrade to full version is not reliable for customers

[MobileVisuals]

I have confirmed that In-app billing is not reliable for other Android 
developers either. 0,5% of all In-app purchases just get lost for them too. 
Another developer has researched this and come to these conclusions: 
1) There are issues with GPS caching of Play servers response, which causes 
IAB to return outdated response.
2) There are issues with multi-account if the user has more than one 
account configured in Google Play. One account used for purchase has to be 
set as default at least once. This is probably a common cause of issues 
when the user is reinstalling an app or installing an app on  or a 
secondary device. 
3) There are other issues, which we don't know the cause of. In some cases 
IAB simply refuses to work. Another developer was able to confirm that with 
one user who installed an APK with some additional debugs and collected 
logs. Managed in-app item wasn't in list returned by getPurchases although 
he clearly owned it. The developer could confirm this in 
payments.google.com console.

I think that this is a very serious issue. Imagine a bank where 0,5% of all 
transactions get lost and those customers loose their money. That is how 
serious this problem is. It makes customers not want to buy apps on Google 
play, because the purchasing process is not reliable. 

On Wednesday, September 21, 2016 at 11:18:04 AM UTC+2, MobileVisuals wrote:
>
> We use managed In-app billing (IAB) in 3 apps. Sometimes there are reports 
> from customers that they don't get the upgrade to full version, eventhough 
> the apps are carefully tested on our test devices on Android 6 and 4.4.4. 
> We test through alpha testing and we have not found any problems with 
> upgrading. 2 of the apps have IAB version 3 and 1 have IAB version 5. It is 
> the same problem. The apps are developed according to IAB guidelines. 
>
> Why does this happen? Is there some problem with Google's servers, which 
> causes these IAB errors, which prevents some customers from getting the 
> upgrade? Has anyone else encountered the same issue?
>
> This is a very serious issue for my company, since it results in bad 
> reviews and lower rankings for the IAB apps. We can not use IAB in the 
> upcoming apps, since it seems to be too unreliable. It is also very 
> annoying that IAB seems to be more reliable on iOS. These are 2 other 
> issues with IAB, which we still haven't found any solution to:
>
>
> http://stackoverflow.com/questions/38481125/consume-purchase-for-in-app-billing-does-not-work-on-android-6
>
> http://stackoverflow.com/questions/38460219/in-app-purchases-are-lost-after-uninstall-on-managed-purchase-type
>
> Here are the statistics about this issue:
>
> app 1: 1215 sold upgrades, 2 complaints from customers who did not get the 
> upgrade
>
> app 2: 94 sold upgrades, 2 complaints from customers who did not get the 
> upgrade
>
> app 3: 122 sold upgrades, 4 complaints from customers who did not get the 
> upgrade
>
> There could be more customers, who did not get the upgrade. The statistics 
> are only for those who complained. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/72ef508f-5b64-4643-8776-dfc7fadd3f3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Re: In-App billing

[Rocky Balboa]

For Android

On Wednesday, July 13, 2016 at 12:33:09 PM UTC+5:30, Rocky Balboa wrote:
>
> How can i implement in_app billing in a sample app without the Google Play 
> Developer Console Account...?
>
> I just want to develop a sample App which contains a list of products for 
> purchases..
> I want to show a fake Dialog box which reveals the product and a price and 
> option to buy the product...
> When the user clicks the buy it should just show the buying is successful 
> and i should be able to see the products owned by the user by calling the 
> getPurchases() method..
> in the log
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/775b8fd9-b22e-4a31-98ef-cb0964c2dbe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Re: In app billing testing issue...

[Naveen]

have a look this u can get here
http://www.androidhub4you.com/2013/03/how-to-inegrate-in-app-purchase-billing.html

On Wednesday, November 5, 2014 2:30:05 PM UTC+5:30, Eden wrote:
>
> Hi,
>
> I followed strictly the android dev instructions to test the IABv3 
> http://developer.android.com/google/play/billing/api.html and also 
> this post instructions 
> http://stackoverflow.com/questions/11068686/this-
> version-of-the-application-is-not-configured-for-billing-
> through-google-pla 
>
> but after waiting more than 48h i have always the same message "the 
> version 
> of the application is not configured for billing through google play". I 
> noticed in logs that the response  with the server is OK...
>
> i have the same problem with my test account with IABv2 and a alpha 
> version 
> of another application
>
> thanks for your your help
>
> eden
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-developers] Re: In-App billing delete subscription items

[Nathan]

True story: 
I have a deprecated product that does not show up in the app. I have gotten 
stray orders anyway. Apparently some people haven't updated the app since 
July. I don't even know how they are buying it because the pre July app 
queried a server that has been decommissioned. 

Inactivating the product had undesirable effects on those who had bought 
when it was still valid. 

I just changed the price to $99. That should stop them.  

Nathan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In-App billing delete subscription items

[Nathan]

On Thursday, December 19, 2013 1:42:38 PM UTC-8, AndroidKing wrote:
>
>
> Thanks Nathan:
> By removing I thought they meant from the developer console and not from 
> the app itself.
>

Ok. When they say "from the product list offered in your app", they mean 
your app's UI. That probably isn't clear enough. 
 

> So once you set a sub you can never move it from the console..
>
>
If it has ever been active, yes. You are simply hiding it from the users. 

Nathan 

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In-App billing delete subscription items

[AndroidKing]

Thanks Nathan:
By removing I thought they meant from the developer console and not from 
the app itself.
So once you set a sub you can never move it from the console..

Ok Thanks...

On Thursday, December 19, 2013 4:04:06 PM UTC-5, AndroidKing wrote:
>
> I can't find a way to do that from the developer console..
> How to I delete a sub item???
>
> I am doing some testing and I created two sub items for testing...
>
> Based on this from Google
>
> http://developer.android.com/google/play/billing/billing_subscriptions.html
>
> it says
>
> "*Important*: You can remove the subscription product from the product 
> list offered in your app to prevent users from seeing or purchasing it."
>
> How to do that...
>
> PS: the sub item is active
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In-App billing delete subscription items

[Nathan]

On Thursday, December 19, 2013 1:04:06 PM UTC-8, AndroidKing wrote:
>
> I can't find a way to do that from the developer console..
> How to I delete a sub item???
>
>
If it has been active, you probably can't do it. Ever. 
 

> I am doing some testing and I created two sub items for testing...
>
> Based on this from Google
>
> http://developer.android.com/google/play/billing/billing_subscriptions.html
>
> it says
>
> "*Important*: You can remove the subscription product from the product 
> list offered in your app to prevent users from seeing or purchasing it."
>
> How to do that...
>

Well, if you wrote your app, surely you know how to *not show* something to 
the users. If you didn't write your app, contact the person who did. 

Nathan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: in-app billing disconnects from activity on configuration change

[Ted Hopp]

But the event is initiated by the user---when the user starts an in-app 
purchase. Also, the IAB flow involves user interaction to complete the 
purchase. The sample 
appthat
 Google provides initiates the purchase from an activity. The in-app 
billing library is designed around a work 
flowthat 
returns results through 
onActivityResult(). There's nothing in the docs for in-app billing that 
suggests this should be done (or how it could be done) by a service.

On Wednesday, September 25, 2013 11:44:53 AM UTC-4, Ian Ni-Lewis wrote:
>
> It seems like the main problem is that you're initiating IAB from an 
> activity, not a service. Activity lifetime is governed primarily by user 
> actions, so an activity is rarely the right container for something that 
> needs to respond to events that aren't initiated by the user.
>
> On Tuesday, September 24, 2013 7:35:26 PM UTC-7, Ted Hopp wrote:
>>
>> In testing an app with in-app billing, we found a nasty problem that 
>> occurs if there is a configuration change while a purchase flow is in 
>> progress. The initiating activity is destroyed and restarted, breaking the 
>> link from Google checkout process to the activity. To the user, it appears 
>> that the purchase flow is intact, but when the purchase is complete, the 
>> activity does not receive a result; hence the app is not informed of the 
>> purchase. This results in a very bad user experience--the user has spent 
>> money, but the app behaves as if it didn't happen! (If the user exits the 
>> app and restarts, it will re-query IAB and notice the change, but that's 
>> not a viable solution.)
>>
>> I suppose I could declare in the manifest that the activity that 
>> initiates the purchase will handle all configuration changes internally, 
>> but that seems rather extreme (not to mention difficult to implement, as we 
>> currently rely on the restart to recreate the activity with the correct 
>> resources).
>>
>> Are there any recommended best practices for how to deal with this?
>>
>> I should note that we also implemented in-app purchasing for the Amazon 
>> Appstore version of the app. Their library does not seem to have the same 
>> problem: the user can start a purchase, change device orientation, and 
>> complete the transaction, and the activity correctly receives the result.
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: in-app billing disconnects from activity on configuration change

[Ian Ni-Lewis]

It seems like the main problem is that you're initiating IAB from an 
activity, not a service. Activity lifetime is governed primarily by user 
actions, so an activity is rarely the right container for something that 
needs to respond to events that aren't initiated by the user.

On Tuesday, September 24, 2013 7:35:26 PM UTC-7, Ted Hopp wrote:
>
> In testing an app with in-app billing, we found a nasty problem that 
> occurs if there is a configuration change while a purchase flow is in 
> progress. The initiating activity is destroyed and restarted, breaking the 
> link from Google checkout process to the activity. To the user, it appears 
> that the purchase flow is intact, but when the purchase is complete, the 
> activity does not receive a result; hence the app is not informed of the 
> purchase. This results in a very bad user experience--the user has spent 
> money, but the app behaves as if it didn't happen! (If the user exits the 
> app and restarts, it will re-query IAB and notice the change, but that's 
> not a viable solution.)
>
> I suppose I could declare in the manifest that the activity that initiates 
> the purchase will handle all configuration changes internally, but that 
> seems rather extreme (not to mention difficult to implement, as we 
> currently rely on the restart to recreate the activity with the correct 
> resources).
>
> Are there any recommended best practices for how to deal with this?
>
> I should note that we also implemented in-app purchasing for the Amazon 
> Appstore version of the app. Their library does not seem to have the same 
> problem: the user can start a purchase, change device orientation, and 
> complete the transaction, and the activity correctly receives the result.
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In app billing and trial query.

[Piren]

Don't enable the in app billing for the trial duration unless you plan on 
spending a lot of time on refunding customers at your expense. 

On Thursday, June 13, 2013 2:30:54 PM UTC+3, Abhi wrote:
>
> Hi,
>I am building an application which I wish to upload to the app store as 
> a paid app. But i would like to post it as a trial app for a set amount of 
> time. I looked at all the options in the app billing version 3. I have 
> found a few problems.
> 1. If I create my app with a non-consumable inapp item then i will not be 
> able to keep it for a set duration as a trial app(Please let me know if my 
> assumption is correct).
> 2. I f I create it via a subscription based model then is there a way I 
> can make the subscriptions last forever and not yearly?
>
> Any help regarding this will be extremely helpful.
>
> Thanks and Regards,
> Abhijeeth Hiliyana
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: [in app billing] Can't add different currency

[kewang]

If I shift localization position in file, the import process never stop.




The file content is following:

premium, published, managed_by_android, false, "zh_TW; test666; YYY; en_US; 
test555; XXX", false, TW; 600; US; 199

kewang於 2013年2月24日星期日UTC+8下午12時21分25秒寫道：
>
> And if I try to import csv method, I got message " The first price is a 
> default price and needs to be defined for Taiwan (TW).
> You cannot set a local price for Taiwan (TW), because this country is not 
> billable in a local currency. "
>
> The following is my csv file. How can I do?
>
> premium, published, managed_by_android, false, "en_US; test555; XXX; 
> zh_TW; test666; YYY", false, US; 199; TW; 600
>
>
> kewang於 2013年2月24日星期日UTC+8上午11時48分58秒寫道：
>>
>> Hi all
>>
>> My app can use in app billing feature and open to the world, but some 
>> users can't buy my product. EX. a German *CAN'T* buy my product, but 
>> other German *CAN*. And his told me "I just cannot choose this option as 
>> it is greyed out with the information: currency not supported."
>>
>> My default currency is USD, and I can't change it to my Country (Taiwan, 
>> TWD). But according to official documentation I should add different 
>> currency. So someone can help me?
>>
>> The following is our conversation history.
>>
>>
>>
>> You should provide the premium version in euro as well. So Europeans can 
>> buy it without credit card! I would buy it for example as I don't have a 
>> credit card!
>> 讚
>>  · 
>>
>>- 
>>
>>
>> 
>>Padfone Launcher 
>> Switcher
>> Hello Danny
>>
>>I have no other setting about specific currency. And buy anything 
>>must should be use credit card at Google Play? If you have no credit 
>> card, 
>>it maybe not buy anything. Or you have compromise idea?
>>
>> 2月20日0:39
>> · 
>> 讚
>>- 
>>
>>
>> 
>>Danny Trunk  I can buy things 
>>without credit card on Google play using my post paid account of my 
>>provider. I just cannot choose this option as it is greyed out with the 
>>information: currency not supported.
>>
>> 2月20日15:33
>>來自手機  · 
>> 已編輯
>> · 
>> 讚
>>- 
>>
>>
>> 
>>Danny Trunk  I've contacted the 
>>Google Support. Maybe they can help us...
>>
>> 2月20日15:59
>> · 
>> 讚
>>- 
>>
>>
>> 
>>Padfone Launcher 
>> Switcher
>> Ok, waiting for Google reply. Can you provide the Google Support 
>>post threads?
>>
>> 2月20日16:13
>> · 
>> 讚
>>- 
>>
>>
>> 
>>Danny Trunk  Sure.
>>
>> 2月20日16:21
>> · 
>> 讚
>>- 
>>
>>
>> 

[android-developers] Re: [in app billing] Can't add different currency

[kewang]

And if I try to import csv method, I got message " The first price is a 
default price and needs to be defined for Taiwan (TW).
You cannot set a local price for Taiwan (TW), because this country is not 
billable in a local currency. "

The following is my csv file. How can I do?

premium, published, managed_by_android, false, "en_US; test555; XXX; zh_TW; 
test666; YYY", false, US; 199; TW; 600


kewang於 2013年2月24日星期日UTC+8上午11時48分58秒寫道：
>
> Hi all
>
> My app can use in app billing feature and open to the world, but some 
> users can't buy my product. EX. a German *CAN'T* buy my product, but 
> other German *CAN*. And his told me "I just cannot choose this option as 
> it is greyed out with the information: currency not supported."
>
> My default currency is USD, and I can't change it to my Country (Taiwan, 
> TWD). But according to official documentation I should add different 
> currency. So someone can help me?
>
> The following is our conversation history.
>
>
>
> You should provide the premium version in euro as well. So Europeans can 
> buy it without credit card! I would buy it for example as I don't have a 
> credit card!
> 讚
>  · 
>
>- 
>
>
> 
>Padfone Launcher 
> Switcher
> Hello Danny
>
>I have no other setting about specific currency. And buy anything must 
>should be use credit card at Google Play? If you have no credit card, it 
>maybe not buy anything. Or you have compromise idea?
>
> 2月20日0:39
> · 
> 讚
>- 
>
>
> 
>Danny Trunk  I can buy things 
>without credit card on Google play using my post paid account of my 
>provider. I just cannot choose this option as it is greyed out with the 
>information: currency not supported.
>
> 2月20日15:33
>來自手機  · 
> 已編輯
> · 
> 讚
>- 
>
>
> 
>Danny Trunk  I've contacted the 
>Google Support. Maybe they can help us...
>
> 2月20日15:59
> · 
> 讚
>- 
>
>
> 
>Padfone Launcher 
> Switcher
> Ok, waiting for Google reply. Can you provide the Google Support post 
>threads?
>
> 2月20日16:13
> · 
> 讚
>- 
>
>
> 
>Danny Trunk  Sure.
>
> 2月20日16:21
> · 
> 讚
>- 
>
>
> 
>Padfone Launcher 
> Switcher
> Do you live in Australia? I just survey about postpaid payment method 
>in au. Telstra is a provider in au, they provide pre-paid/post-paid buy 
>android app last year.
>
>Maybe you can contact your provider about how to buy android app.
>
> 2月20日16:47

[android-developers] Re: In-app Billing v3 - "user is not eligible for this purchase"

[rudas]

And then it suddenly started working... a day after uploading the .apk.

It should be noted that I tried a workaround suggested on the Internet.
I uploaded a new .apk using old developer console design.
But after a couple of hours I did not notice any difference, but now (~4 
hours later it works)

So maybe this is a problem related to the new developer console... which 
Google definitely need to fix in that case!
 

Den fredagen den 8:e februari 2013 kl. 14:28:10 UTC+1 skrev rudas:
>
> Hi all,
>
> I have implemented the new billing API suggested by Google and used the 
> trivialdrive demo as a template.
> But I'm not able to purchase my in-app item. As soon as I'm redirected to 
> the Play store I get the following error message "user is not eligible for 
> this purchase"
>
> Implementation details:
> TRIVIAL DRIVE - SAMPLE FOR IN-APP BILLING VERSION 3
> (Basically I'm only using the "premium" part of the sample.)
>
> I have followed all steps in the readme provided in the sample code. (E.g. 
> application specific key etc. etc.)
> I added my personal google account as a "Test account" on my publisher 
> account.
> I have also tested it a day after adding uploading the .apk file to the 
> developer console
>
> Same problem is seen on two devices using separate accounts, both added as 
> "Test accounts". 
>
>
> Please help sort this out.
> I really wonder why in-app billing must be sooo diificult to test, it's 
> really frustrating working with this.. 
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In-app billing V3 - "Error while retrieving information from server. [RPC:S-7:AEC-0]"

[Kostya Vasilyev]

A Google search for "RPC:S-7:AEC-0" shows a lot of discussions of this 
error. Not sure if any "magic" fixes would work though -- I think your 
best bet is to report this to Google developer support.

https://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=136601

-- K

On Monday, January 28, 2013 4:07:32 PM UTC+4, Rajan wrote:
>
> i have create one app and already published in that app i used in-app 
> billing (UNMANAGED).
>
> When i test it using "android.test.purchased" product id, it will works 
> properlly, but after publishing the app i test it again using live product 
> Id at that time it will not working, means my app redirect to google play 
> store after that it returns this kind of Error in popup message and that 
> message is :
>
> "Error while retrieving information from server. [RPC:S-7:AEC-0]"
>
> I Have do all the things like Factory Reset, Removeing Google A/c , 
> Restart the phone etc. but not getting any success.
>
> please help me i'm stuck since last 4 to 5 days i didn't get any solution 
> yet.
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group, send email to 
android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Re: In App Billing Error

[Kandarp "Ken" Patel]

Finally solved my "User is not eligible..." situation.

In my case it came down to this change in the licensing system:

The *Licensing keys* are now managed for each app individually. To see the 
license 
key for an application, switch to the new 
design and 
go to the *Services and APIs* for 
the application

I had been using the old license key (which used to be shared across apps) 
in my new app.  I finally found this little note on the Google play page, 
switched to the new design, went to Services and APIs, and got the new 
"app-specific" license key, and entered that into my app, and now 
everything functions as it should.

Hope this helps!
Ken



On Friday, December 14, 2012 9:54:38 PM UTC-8, ajmer singh wrote:
>
> Hi All
>
> I am implementing In app billing(Version 3) in android app. 
>
>1. I had put the Signed apk on the Play Store.
>2. Also had a managed Product Activated.
>3. Using a Signed apk for testing on phone.  
>4. Managed Product is also showing up in my Query for the inventory.
>5. Also created and using a Google account for Testing In app Billing. 
>
>
> Still getting the "Item Unavailable" and "User is not eligible for this 
> purchase" , Please refer to attached Screen shot for more details ,Please 
> anybody here who has got this type of error please help.
>
> -- 
> Thanks and Regards
> Ajmer Singh
>  

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing Error

[Ajmer Singh]

Hi All

I get this resolved, Mistake that i had done is:


   1. That i entered an test account under the setting in Google Developer
   Console.This is ok.
   2. Then change the selection of Drop down named the "Licensed Test
   Response" to Licensed test response.
   3. Please have a look at the attached images.


On Fri, Dec 21, 2012 at 5:04 PM, Lev Stipakov  wrote:

> Thanks, but I am using billing V3 and my code is based on trivialdriving
> example.
>
> perjantai, 21. joulukuuta 2012 11.52.15 UTC+2 Grzegorz Patynek kirjoitti:
>
>> there is an error in dungeons application from google.
>> you may find answer somewhere in stackoverflow.
>>
>> W dniu piątek, 21 grudnia 2012 09:30:50 UTC+1 użytkownik Lev Stipakov
>> napisał:
>>>
>>> Well, 12 hrs ago uploaded a new app, added products and got the same
>>> problem.
>>>
>>> Would be nice to get some comments from Google.
>>>
>>> perjantai, 21. joulukuuta 2012 6.12.02 UTC+2 sandy M kirjoitti:

 Please let me know if get of it!! I too facing the same buddy
>>>
>>>  --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
Thanks and Regards
Ajmer Singh

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en<>

Re: [android-developers] Re: In App Billing Error

[Lev Stipakov]

Thanks, but I am using billing V3 and my code is based on trivialdriving 
example.

perjantai, 21. joulukuuta 2012 11.52.15 UTC+2 Grzegorz Patynek kirjoitti:
>
> there is an error in dungeons application from google. 
> you may find answer somewhere in stackoverflow. 
>
> W dniu piątek, 21 grudnia 2012 09:30:50 UTC+1 użytkownik Lev Stipakov 
> napisał:
>>
>> Well, 12 hrs ago uploaded a new app, added products and got the same 
>> problem.
>>
>> Would be nice to get some comments from Google.
>>
>> perjantai, 21. joulukuuta 2012 6.12.02 UTC+2 sandy M kirjoitti:
>>>
>>> Please let me know if get of it!! I too facing the same buddy 
>>
>>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing Error

[Grzegorz Patynek]

there is an error in dungeons application from google. 
you may find answer somewhere in stackoverflow. 

W dniu piątek, 21 grudnia 2012 09:30:50 UTC+1 użytkownik Lev Stipakov 
napisał:
>
> Well, 12 hrs ago uploaded a new app, added products and got the same 
> problem.
>
> Would be nice to get some comments from Google.
>
> perjantai, 21. joulukuuta 2012 6.12.02 UTC+2 sandy M kirjoitti:
>>
>> Please let me know if get of it!! I too facing the same buddy 
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing Error

[Lev Stipakov]

Well, 12 hrs ago uploaded a new app, added products and got the same 
problem.

Would be nice to get some comments from Google.

perjantai, 21. joulukuuta 2012 6.12.02 UTC+2 sandy M kirjoitti:
>
> Please let me know if get of it!! I too facing the same buddy 

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing Error

[Sandeep Venkat]

Please let me know if get of it!! I too facing the same buddy

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing Error

[Lev Stipakov]

I had the same problem which was resolved by itself several hours after 
I've uploaded app.

lauantai, 15. joulukuuta 2012 7.54.38 UTC+2 ajmer singh kirjoitti:
>
> Hi All
>
> I am implementing In app billing(Version 3) in android app. 
>
>1. I had put the Signed apk on the Play Store.
>2. Also had a managed Product Activated.
>3. Using a Signed apk for testing on phone.  
>4. Managed Product is also showing up in my Query for the inventory.
>5. Also created and using a Google account for Testing In app Billing. 
>
>
> Still getting the "Item Unavailable" and "User is not eligible for this 
> purchase" , Please refer to attached Screen shot for more details ,Please 
> anybody here who has got this type of error please help.
>
> -- 
> Thanks and Regards
> Ajmer Singh
>  

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing Error

[Ajmer Singh]

Here is the attached Screen Shot.

On Sat, Dec 15, 2012 at 11:24 AM, Ajmer Singh wrote:

> Hi All
>
> I am implementing In app billing(Version 3) in android app.
>
>1. I had put the Signed apk on the Play Store.
>2. Also had a managed Product Activated.
>3. Using a Signed apk for testing on phone.
>4. Managed Product is also showing up in my Query for the inventory.
>5. Also created and using a Google account for Testing In app Billing.
>
>
> Still getting the "Item Unavailable" and "User is not eligible for this
> purchase" , Please refer to attached Screen shot for more details ,Please
> anybody here who has got this type of error please help.
>
> --
> Thanks and Regards
> Ajmer Singh
>



-- 
Thanks and Regards
Ajmer Singh

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en<>

[android-developers] Re: In-App billing draft apk not appearing in Developer Console

[jb]

I'm using the old developer console.

jb

>
>>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App billing draft apk not appearing in Developer Console

[jb]

I'm using the old developer console.

On Thursday, December 6, 2012 5:16:48 PM UTC-8, MathieuB wrote:
>
> Are you using the new or old developer console? I've noted some 
> functionality missing in the new interface.
>
> On Thursday, December 6, 2012 5:55:01 PM UTC-5, jb wrote:
>>
>> Hi,
>>
>> I'm trying to test In-App billing on my app.
>> I registered a test account in my Google Play account.
>>
>> I uploaded a new, signed apk as an unpublish draft (I uploaded and saved, 
>> but did not publish)
>> The VersionCode is greater than the published apk (49 vs 48)
>> The VersionName is different than the published apk (1.1.20 vs 1.1.19)
>>
>> The new apk contains: com.android.vending.BILLING
>>
>> When I go back to the Developer Console screen, the draft apk does not 
>> appear, only the published apks are present.
>>
>> Am I missing a step?
>>
>> jb
>>
>>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App billing draft apk not appearing in Developer Console

[MathieuB]

Are you using the new or old developer console? I've noted some 
functionality missing in the new interface.

On Thursday, December 6, 2012 5:55:01 PM UTC-5, jb wrote:
>
> Hi,
>
> I'm trying to test In-App billing on my app.
> I registered a test account in my Google Play account.
>
> I uploaded a new, signed apk as an unpublish draft (I uploaded and saved, 
> but did not publish)
> The VersionCode is greater than the published apk (49 vs 48)
> The VersionName is different than the published apk (1.1.20 vs 1.1.19)
>
> The new apk contains: com.android.vending.BILLING
>
> When I go back to the Developer Console screen, the draft apk does not 
> appear, only the published apks are present.
>
> Am I missing a step?
>
> jb
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing: making sense of errors in the logs.

[bob]

Maybe the 500 refers to this HTTP code?

Internal Error 500
The server encountered an unexpected condition which prevented it from 
fulfilling the request.

Maybe try again later?


On Thursday, November 1, 2012 11:05:44 PM UTC-5, Bram Stolk wrote:
>
> Hi,
>
> I am integrating In App Billing, going by the Dungeons example from the 
> SDK.
> android.test.purchased works for me, but when getting my own products, it 
> fails.
>
> I try to make sense of the errors in the logs.
> There are so many to choose from.
>
> Some info on my setup:
> - I test with proper test account, as added to Google Play console.
> - Test user has working google wallet and can purchase published 3rd party 
> apps.
> - Test device is up to date Acer A100
> - BILLING permission is spec'd in the Manifest.
> - I use the same app version for testing, as was uploaded to google.
> - Product was marked as active in Google Play Console.
> - I get a positive result back when I check for Billing Supported.
>
> My questions:
> (1) What does this mean: *Saving carrier billing params failed*
> (2) What is the significance of:* Attempt to delete 
> 'paramsPMEA2H1cBHnCGCAFXApRbQ' failed!*
> (3) What target is referred to in *The target server failed to respond*?
> (4) What is *Unexpected response code 500*?
> (5) And finally: what is *[DF-BPA-13]*? This code actually shows up in a 
> dialog on the device.
>
> D/BillingService( 2501): RequestPurchase
> D/Finsky  ( 2188): [271] MarketBillingService.getPreferredAccount: 
> com.steenriver.littlecrane: Account from first account.
> D/Finsky  ( 2188): [271] MarketBillingService.getPreferredAccount: 
> com.steenriver.littlecrane: Account from first account.
> I/ActivityManager(  144): START {act=android.intent.action.VIEW 
> cmp=com.android.vending/com.google.android.finsky.activities.IabActivity 
> (has extras)} from pid -1
> D/BillingService( 2501): request id: 1802264350828807725
> V/threaded_app( 2501): SaveInstanceState: 0x52a1b0
> I/crane   ( 2501): State saved
> V/threaded_app( 2501): APP_CMD_SAVE_STATE
> V/threaded_app( 2501): Pause: 0x52a1b0
> V/threaded_app( 2501): activityState=13
> V/threaded_app( 2501): WindowFocusChanged: 0x52a1b0 -- 0
> D/Finsky  ( 2188): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping 
> self-update. Local Version [8015016] >= Server Version [0]
> I/ActivityManager(  144): Displayed 
> com.android.vending/com.google.android.finsky.activities.IabActivity: +73ms
> W/Finsky  ( 2188): [1] CarrierParamsAction.run: Saving carrier billing 
> params failed.
> E/Finsky  ( 2188): [294] FileBasedKeyValueStore.delete: Attempt to delete 
> 'paramsPMEA2H1cBHnCGCAFXApRbQ' failed!
> D/Finsky  ( 2188): [1] GetBillingCountriesAction.run: Skip getting fresh 
> list of billing countries.
> I/ActivityManager(  144): Start proc com.google.android.gsf.login for 
> service 
> com.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginService:
>  
> pid=2516 uid=10036 gids={3003, 1015, 1007, 2001, 3006}
> I/ElegantRequestDirector( 2188): I/O exception 
> (org.apache.http.NoHttpResponseException) caught when processing request: 
> The target server failed to respond
> I/ElegantRequestDirector( 2188): Retrying request
> I/ElegantRequestDirector( 2188): I/O exception 
> (org.apache.http.NoHttpResponseException) caught when processing request: 
> The target server failed to respond
> I/ElegantRequestDirector( 2188): Retrying request
> D/dalvikvm( 2188): GC_CONCURRENT freed 559K, 8% free 7736K/8391K, paused 
> 3ms+7ms
> E/Volley  ( 2188): [277] BasicNetwork.performRequest: Unexpected response 
> code 500 for 
> https://android.clients.google.com/fdfe/details?doc=inapp:com.steenriver.littlecrane:premium
> D/DfeApi  ( 2188): [1] DfeRequest.deliverError: Not delivering error 
> response for request=[[ ] 
> https://android.clients.google.com/fdfe/details?doc=inapp:com.steenriver.littlecrane:premiumNORMAL
>  8], error=[DisplayErrorMessage[Error retrieving information from 
> server. [RPC:AEC:0]]] because response already delivered.
> E/Volley  ( 2188): [276] BasicNetwork.performRequest: Unexpected response 
> code 500 for https://android.clients.google.com/fdfe/purchase
> W/Finsky  ( 2188): [1] CheckoutPurchase.onErrorResponse: 
> DisplayErrorMessage[Error processing purchase. [DF-BPA-13]]
> E/Finsky  ( 2188): [1] CheckoutPurchase.setError: type=UNKNOWN, code=-1, 
> message=Error processing purchase. [DF-BPA-13]
>
> Many thanks!
>
>   Bram Stolk
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing for canadian

[MathieuB]

Finally, it seems I was wrong and i'm really happy to notice it!

I was registered as a developer on our dev console but wasn't the admin. 
When I was trying to register the google checkout account, I was going 
directly to checkout.google.com and it said Canada wasn't supported.

Today I try with the admin account and there were the option in the dev 
console to open the account and everything works! :)

Thank you for your help guys.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing for canadian

[MathieuB]

Hi,

Ok guys, i'm glad to hear that.

I'll try to investigate more and find what is causing the issue. Weird 
thing is i'm not the only one reporting that problem. I found on other 
forums that people in Canada receive the message "Canada is not supported" 
when trying to register a merchant account.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing for canadian

[Thomas Bouron]

Hi!

I got a Developer account and a merchant account in Spain (same in France).
I didn't experienced any issue when I first created it. BTW, my In-app 
billing works well.

I think your issue is located somewhere else.

On Saturday, October 13, 2012 6:31:13 PM UTC+2, MathieuB wrote:
>
> Hello,
>
> I'm a canadian developer working on an android app. It is currently free 
> on the google play store.
>
> The strategy for this app, from the beginning, was to someday implement 
> in-app billing. So the user download the free app, goes through a list of 
> items, some free and some not, usual pattern. Today I was beginning to look 
> at implementing in-app billing, when I faced the fact that canadian CANNOT 
> open google merchant account... I was a bit shocked.
>
> So i'm looking at alternative now. I know Paypal X have an api, but it 
> seems this is going against google play policies not to use their system.
>
> I'm a bit stuck with it. If google cannot allow canadian to use in-app 
> billing, would they allow us to use paypal system for in-app purchase? 
>
> Developers/publishers not from US or UK, what have you done with your app 
> to sell items in-app? 
>
> Thank you in advance!
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing V2: Item not found, but purchase OK

[Michele Diblasi]

hi, I seem to be having the same problem. But after the message "ITEM NOT 
FOUND" google wallet asks for the correct money and the correct item.  
However, upon clicking "ACCEPT" to make the purchase I get message "YOUR 
ORDER CANNOT BE PROCESSED, PLEASE TRY AGAIN".  Did you have the same? Is 
the problem gone entirely?
Thank you,
Michele Diblasi
 
On Saturday, 16 June 2012 06:23:02 UTC+2, John wrote:

> Have In App Billing V2 incorporated into my code and be able to buy 
> one-time purchase item and yearly subscription item. But when 
> purchasing one-time purchase item, always get the message "Item not found". 
> Is this a Google bug? Any help? Thanks in advance. 
>
> -John
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: in-app billing is possible through Paypal A/c.

[Calin Perebiceanu]

Quote from  
http://developer.android.com/guide/google/play/billing/index.html 

*In-app Billing is a Google Play* service that lets  ..

I think this says it all.

On Thursday, 13 September 2012 09:31:33 UTC+3, Rajan wrote:
>
> hi all,
>
> i want to use *in-app billing* as a paid service, but for that 
>
> i don't want to use Google PLAY (App market) or i don't want to go through 
> Google PLAY.
>
> it must be done through the user's Paypal account. 
>
> is it possible (Programmatically) ??
>
> if YES than please provide me any link or any sample example.
>
> i really want to know this things.
>
> Guys please help me. 
>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing Limits

[sam]

I can't find the answer in any documentation. Do you know the reason
for the limit?

Other apps circumvent the limit. Its quite common in games to buy
credits. If thats ok then it would be simple to get around.

On Jul 12, 9:25 am, Anton Kaiser  wrote:
> I can't tell you about the limit (must be documented in the API reference
> or some developer tutorial on In App Billing).
> If there is a good reason for the limit, Google won't hesitate to remove
> your app from Google Play if you try to circumvent that limit.
>
> Am Mittwoch, 11. Juli 2012 15:05:09 UTC+2 schrieb sam:
>
>
>
>
>
>
>
>
>
> > I would like to know what the maximum number of items that can be
> > placed in In App billing for both Android. 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?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing Limits

[Anton Kaiser]

I can't tell you about the limit (must be documented in the API reference 
or some developer tutorial on In App Billing).
If there is a good reason for the limit, Google won't hesitate to remove 
your app from Google Play if you try to circumvent that limit.


Am Mittwoch, 11. Juli 2012 15:05:09 UTC+2 schrieb sam:
>
> I would like to know what the maximum number of items that can be 
> placed in In App billing for both Android. 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?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing RESULT_ERROR

[Zvi Rabinovich]

Hi,

Sorry in advance for not adding new real information to this.

But, I've noticed that the post is old and I was wondering whether you 
successfully solved this issue.
We are currently running our first in-app integrated app and experiencing 
the same pains.

Thanks,
Zvi

On Wednesday, December 28, 2011 3:17:56 PM UTC+2, deve...@pawprintgames.com 
wrote:
>
> Hi there, 
>
> I recently launched an application on the Android Market which 
> includes In App Billing. I have tested this functionality both whilst 
> developing, using a test account and once the application went live on 
> the market (using a non test account, on a completely different mobile 
> phone) and for me it works successfully: the game credits acknowledges 
> the purchase and awards the user accordingly and my Google checkout 
> credits me the correct amount of money. However, it appears this 
> functionality is not working for everyone, I know this because I have 
> analytics inside the game that report when the user attempts to 
> purchase something and what the result of the purchase attempt was, in 
> the last 24 hours I have had 9 attempts of using the in app billing 
> which resulted in: 
>
> 8 X RESULT_ERROR 
> 1 X RESULT_SERVICE_UNAVAILABLE 
>
> My application handles these cases 'correctly' by informing the user 
> the purchase attempt failed, but I wondered if there is anything I 
> should worry about? Since going live, the application hasn't had any 
> successful in app billing attempts, but only in the latest version 
> have I added the extra analytics to log the reasons why. I have looked 
> up the above errors in the documentation and it lists them as: 
>
> RESULT_SERVICE_UNAVAILABLE - Indicates that the network connection is 
> down 
> RESULT_ERROR - Indicates an unexpected server error. For example, this 
> error is triggered if you try to purchase an item from yourself, which 
> is not allowed by Google Checkout 
>
> There is also other references in the documentation for RESULT_ERROR 
> as: 
>
> RESULT_ERROR  - There was an error connecting with the Android Market 
> application 
>
> For the service unavailable, I can appreciate perhaps the user was out 
> of signal when they attempted to purchase, or were on a non phone with 
> WiFi disabled etc. but the RESULT_ERROR I am not sure about. There 
> seem to be multiple descriptions for this error, the unable to connect 
> to Android Market application error makes me wonder if the user has 
> downloaded a copy of the application from a non authorised source and 
> as such market place isn't talking to it properly. 
>
> I appreciate have rambled on a little here, and perhaps not really 
> asked a direct question, but can anyone possibly advise me with 
> regards to whether I have a problem here or not? Has anyone else used 
> In App Billing and had similar results? Is there any way to get 
> further information about what caused a RESULT_ERROR for example? 
>
> I don't wish to be seen as self promoting my application, but if it 
> helps diagnose this issue, a link to the application follows: 
>
>
> https://market.android.com/details?id=com.pawprintgames.kamicrazy.global&hl=en
>  
>
> Many thanks, 
>
> Steve

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing – get price paid after successful purchase?

[hzhao]

I found a way to use 
Google Checkout XML API - Notification History 
API
to get the order's detail at backend.

Try it with the orderId  you got from the notice


On Sunday, May 8, 2011 3:40:46 AM UTC+8, Rob B wrote:
>
> Is it possible to obtain the actual transaction cost after a 
> successful purchase occurs? The first paragraph of the In-app Billing 
> Overview page (http://developer.android.com/guide/market/billing/ 
> billing_overview.html)
>  
> says "When the checkout process is complete, 
> the service sends your application the purchase details, such as the 
> order number, the order date and time, and the price paid." However, 
> the JSON dict that comes with PURCHASE_STATE_CHANGED (after sending 
> GET_PURCHASE_INFORMATION to the Market) doesn't seem to include 
> anything about cash spent. 
>
> Additionally, it would be useful to be able to query the Market to 
> obtain all purchasable items, but it seems that others have already 
> pointed out that this doesn't exist and there's no solution but to 
> hardcode it. 
>
> Any help on these topics would be greatly appreciated.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing V2: Item not found, but purchase OK

[John]

Appreciate your help !!

-John

On Friday, July 6, 2012 8:15:56 PM UTC-7, fibercode wrote:
>
> This is a bug in the sample Dungeons application in the onClick method for 
> the purchase button.
>
> I posted a solution here:
> http://stackoverflow.com/a/11371927/625030
>
> The supplied method has a bug in the if {} else if {} statement where it 
> causes the mBillingService.requestPurchase to be called twice, when the 
> selected item is not a subscription item (mManagedType != 
> Managed.SUBSCRIPTION). So the same item will be requested twice, once with 
> an item type of "inapp" (which is the valid request) and immediately after 
> that with an item type of "subs" (which is incorrect and it shows "item not 
> found").
>
> Here is the buggy code:
>
> if (mManagedType != Managed.SUBSCRIPTION &&
> !mBillingService.requestPurchase(mSku, 
> Consts.ITEM_TYPE_INAPP, mPayloadContents)) {
> showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
> } else if (!mBillingService.requestPurchase(mSku, 
> Consts.ITEM_TYPE_SUBSCRIPTION, mPayloadContents)) {
> // Note: mManagedType == Managed.SUBSCRIPTION
> showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID);
> }
>
> To fix this, add mManagedType == Managed.SUBSCRIPTION to the else if above.
>
> Here is how the function should look:
>
> @Override
> public void onClick(View v) {
> if (v == mBuyButton) {
> if (Consts.DEBUG) {
> Log.d(TAG, "buying: " + mItemName + " sku: " + mSku);
> }
>
> if (mManagedType != Managed.SUBSCRIPTION &&
> !mBillingService.requestPurchase(mSku, 
> Consts.ITEM_TYPE_INAPP, mPayloadContents)) {
> showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
> } else if (mManagedType == Managed.SUBSCRIPTION && 
> !mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_SUBSCRIPTION, 
> mPayloadContents)) {
> // Note: mManagedType == Managed.SUBSCRIPTION
> showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID);
> }
> } else if (v == mEditPayloadButton) {
> showPayloadEditDialog();
> } else if (v == mEditSubscriptionsButton) {
> editSubscriptions();
> }
> }
>
>
> On Saturday, 16 June 2012 00:23:02 UTC-4, John wrote:
>>
>> Have In App Billing V2 incorporated into my code and be able to buy 
>> one-time purchase item and yearly subscription item. But when 
>> purchasing one-time purchase item, always get the message "Item not found". 
>> Is this a Google bug? Any help? Thanks in advance.
>>
>> -John
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing V2: Item not found, but purchase OK

[fiber]

This is a bug in the sample Dungeons application in the onClick method for 
the purchase button.

I posted a solution here:
http://stackoverflow.com/a/11371927/625030

The supplied method has a bug in the if {} else if {} statement where it 
causes the mBillingService.requestPurchase to be called twice, when the 
selected item is not a subscription item (mManagedType != 
Managed.SUBSCRIPTION). So the same item will be requested twice, once with 
an item type of "inapp" (which is the valid request) and immediately after 
that with an item type of "subs" (which is incorrect and it shows "item not 
found").

Here is the buggy code:

if (mManagedType != Managed.SUBSCRIPTION &&
!mBillingService.requestPurchase(mSku, 
Consts.ITEM_TYPE_INAPP, mPayloadContents)) {
showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
} else if (!mBillingService.requestPurchase(mSku, 
Consts.ITEM_TYPE_SUBSCRIPTION, mPayloadContents)) {
// Note: mManagedType == Managed.SUBSCRIPTION
showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID);
}

To fix this, add mManagedType == Managed.SUBSCRIPTION to the else if above.

Here is how the function should look:

@Override
public void onClick(View v) {
if (v == mBuyButton) {
if (Consts.DEBUG) {
Log.d(TAG, "buying: " + mItemName + " sku: " + mSku);
}

if (mManagedType != Managed.SUBSCRIPTION &&
!mBillingService.requestPurchase(mSku, 
Consts.ITEM_TYPE_INAPP, mPayloadContents)) {
showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
} else if (mManagedType == Managed.SUBSCRIPTION && 
!mBillingService.requestPurchase(mSku, Consts.ITEM_TYPE_SUBSCRIPTION, 
mPayloadContents)) {
// Note: mManagedType == Managed.SUBSCRIPTION
showDialog(DIALOG_SUBSCRIPTIONS_NOT_SUPPORTED_ID);
}
} else if (v == mEditPayloadButton) {
showPayloadEditDialog();
} else if (v == mEditSubscriptionsButton) {
editSubscriptions();
}
}


On Saturday, 16 June 2012 00:23:02 UTC-4, John wrote:
>
> Have In App Billing V2 incorporated into my code and be able to buy 
> one-time purchase item and yearly subscription item. But when 
> purchasing one-time purchase item, always get the message "Item not found". 
> Is this a Google bug? Any help? Thanks in advance.
>
> -John
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[SXC]

I am a consumer and I have encountered this problem quite a few times. I'm 
not too sure if it mainly caused by the reasons I stated below but here are 
my share. And my phone is a rooted Galaxy Nexus.

This issue only happened when I attempt to use my Australian credit card to 
purchase apps/music/movies in USD (by link a US billing address to credit 
card in Google Wallet). In the past, it worked for all contents in Android 
Market. Since this year, buying musics and renting movies in this way will 
lead payment authorisation not responding, then order canceled 
automatically just like everyone reported. Then my whole account purchase 
function will be suspended until I manually lodge verification documents to 
Google Wallet and they manually re-activated my Google Wallet. This is 
really annoying. Even worse, since today I found buying apps are facing the 
same problem.

I made this attempt due 2 reasons. One is some contents are only available 
in US market and I want to buy them. I normally use market enabler apps+VPN 
to switch to US Play Store and make the purchase. The other reason is 
because some app price are set more expensive in non-US market, eg, 
Australia. Since I use my Australian credit card to purchase apps in USD, I 
will only be charged the equivalent amount of the app's US price (some time 
Euro price like EA Netherlands apps).

I'm still not sure if this "Took too long to delivery" is caused by the 
credit company authorisation or not. But I'm just quite unhappy as Google 
not listening and do not do any improve. Every time when I have to 
re-activate my Google Wallet I will pass along a long letter to suggest 
them improve or introduce prepaid card like Apple appstore, No one 
listened. And how come until yesterday it was still OK to purchasing apps 
in way while others not, there are must be some Google's setting that 
blocked this. Couldn't understand why Google block people from outside US 
buying contents.

>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing V2: Item not found, but purchase OK

[johnjzhu]

http://stackoverflow.com/questions/10775008/in-app-billing-item-not-found/11105814#11105814

On Tue, Jun 19, 2012 at 9:37 AM, John  wrote:

> Yes. Still have the problem even after the reboot. It occurs on multiple
> phones (all my phones and tablets).
>
>
> On Monday, June 18, 2012 11:11:42 AM UTC-7, John wrote:
>>
>> Are you still having this problem? I found I had to reboot the phone for
>> some reason, after publishing the item for in app billing.
>
>  --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
Best Regards,
-John

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing V2: Item not found, but purchase OK

[John]

Yes. Still have the problem even after the reboot. It occurs on multiple 
phones (all my phones and tablets).

On Monday, June 18, 2012 11:11:42 AM UTC-7, John wrote:
>
> Are you still having this problem? I found I had to reboot the phone for 
> some reason, after publishing the item for in app billing.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing V2: Item not found, but purchase OK

[John]

Are you still having this problem? I found I had to reboot the phone for 
some reason, after publishing the item for in app billing.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing SecurityException: caller uid XXXXX is different than the authenticator's uid

[Liorry]

never mind, custom ROM issue.

On Monday, April 16, 2012 4:11:56 PM UTC+3, Liorry wrote:
>
> I'm trying to implement the in-app billing feature in my app. 
>
> I did everything the tutorial suggested: 
>
> * Implemented the sample app in my app 
> * Changed all the packages names and added my public key in the 
> Security.class 
> * Added a test account and made sure it's the default account in the 
> device I use for testing 
> * Published the 2 items (sword and potion) under my unpublished app, 
> as suggested. 
>
> Still getting this error: 
> SecurityException: caller uid X is different than the 
> authenticator's uid 
> Could not retrieve Checkout auth token 
>
> Anyone encountered this error and knows how to solve it? 
>
> Thank you!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Kostya Vasilyev]

Here is another idea:

If a user has an existing order that's been placed on hold, and tries to 
place another one (and another and another, as some try to do)...


... Market could display a message explaining what's going on.

Oh, no-one from the Market team reads this list. Sorry, I got carried away.

-- Kostya


On 02/15/2012 12:00 AM, John Coryat wrote:
Call me crazy, but wouldn't it be a lot more helpful to the user if 
the error message displayed to them contained the line:


"Attempting the purchase again 24 hours later should work correctly."

Then again, what do I know?

-John Coryat
Science and Technology News Aggregator
Twitter: http://twitter.com/coryat
G+: http://www.usnaviguide.com/+


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Kostya Vasilyev]

On 02/15/2012 12:00 AM, John Coryat wrote:
Call me crazy, but wouldn't it be a lot more helpful to the user if 
the error message displayed to them contained the line:


"Attempting the purchase again 24 hours later should work correctly."


Hmm...

And sending a new in-app purchase notification once the order is 
reviewed and reinstated?


And another email to the user if not? ( something like "Sorry, your 
account is on hold, you can't make purchases anymore" )




Then again, what do I know?


A message like that would make users think it's not the app's fault - 
perhaps there is something wrong with that.


Then again, there could be a technical reason, such as Google lacking 
the bandwidth to send so many emails?




-John Coryat
Science and Technology News Aggregator
Twitter: http://twitter.com/coryat
G+: http://www.usnaviguide.com/+



--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Dallas Gutauckis]

On Tue, Feb 14, 2012 at 15:00, John Coryat  wrote:

> Call me crazy, but wouldn't it be a lot more helpful to the user if the
> error message displayed to them contained the line:


There are a number of different things that could help for this... I'm just
happy to have gotten some sort of feedback on the issue.


>
> "Attempting the purchase again 24 hours later should work correctly."
>
> Then again, what do I know?
>
> -John Coryat
> Science and Technology News Aggregator
> Twitter: http://twitter.com/coryat
> G+: http://www.usnaviguide.com/+
>
>  --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[John Coryat]

Call me crazy, but wouldn't it be a lot more helpful to the user if the 
error message displayed to them contained the line:

"Attempting the purchase again 24 hours later should work correctly."

Then again, what do I know?

-John Coryat
Science and Technology News Aggregator
Twitter: http://twitter.com/coryat
G+: http://www.usnaviguide.com/+

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Dallas Gutauckis]

Through email feedback from an Android Developer Advocate, I have confirmed 
that this is a risk/settlement issue.

Full response from him:

"Dallas, 
I'm sorry to hear that you've been having difficulty getting adequate 
support for this issue. My apologies.

The issue you describe is currently a known issue. Your assessment was 
correct when you said that this was a settlement/risk issue.

Specifically, these users are being flagged by Google Checkout as being in 
a "risk bin" by our automated systems. These users' orders are temporarily 
delayed while we manually investigate the account. In the majority of 
cases, the orders are released for processing within 24 hours without 
problem.

In-app billing is a special case, as all in-app billing orders are subject 
to a 45 second processing timeout. (This was based on feedback from several 
prominent app developers.) Unfortunately, this means that any user who is 
placed into a risk bin will have their order canceled. Attempting the 
purchase again 24 hours later should work correctly.

In particular, all the orders mentioned in your bug report are from the 
same user, whose account is currently listed as "On Hold" while a risk 
review is completed. (Note that accounts used for developer testing are 
much more likely to get flagged for risk review, as they tend to display 
anomalous purchasing patterns.)

Again, the Market team is aware of this issue and is actively working on 
improving the customer experience. 
Thanks for your patience."


And through further communication, it came down to:

"Dallas,
It's the individual users ("buyer accounts") who are buying from that 
account that are temporarily placed on hold. The account used for 
publishing ("merchant account") itself is unaffected -- most users will not 
have problems placing orders for your apps.

Hope that helps clarify things." 

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Nikolay Elenkov]

On Sun, Feb 5, 2012 at 2:24 AM, Nikolay Elenkov
 wrote:
> 2012/2/5 Kostya Vasilyev :
>> 4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov
>>  написал:

>>
>>
>> Unavoidable?
>>
>> Does the rest of the world's e-commerce suffer the same failures?
>
> They must be :) I was referring to the answer I quoted. It says that
> when credit authorization is put on hold at the credit company or carrier
> (if using carrier billing) for some reason, Google checkout will eventually
> time out and cancel the transaction. Quote: "It's not a bug, it's the spec".
> Since it's actually out of their control, some orders will be cancelled
> occasionally. The problem is that apparently it's happening rather
> often for some people.
>

And Google Checkout is at it again... Apparently happens more often
around the middle of the month, when carriers process payments/credit
authorizations. Same period for credit card companies? Any way you
look at it, it's baaadly broken.

Happy Valentine's day/wine day or whatever you are celebrating today :)

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In App Billing RESULT_ERROR

[develo...@pawprintgames.com]

Sorry to bump this post, but I wondered if anyone had any thoughts on
this issue? My analytics are now showing that my failures count in at:

323 times : RESULT_ERROR
019 times : RESULT_SERVICE_UNAVAILABLE

I also have around a dozen or less successes and around 2.5k cancels.
I can appreciate that for the cancels a lot of people will click to
get more information about the IAP and then decide to cancel, but I am
still very eager to further diagnose the errors listed above.

Any help you can provide would be gratefully received.

Best regards,

Steve

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Dallas Gutauckis]

I'm also seeing this issue with any card I test with, on any account I test 
with, and on any device I test with.

http://stackoverflow.com/questions/9164013/in-app-billing-fails-with-took-too-long-to-deliver

Quoted from SO:

I am in the process of integrating In-App Billing in my application for 
unmanaged products. I've configured my application in the market already to 
implement the BILLING permission. I've published the product ids as 
expected by my in-development version of my application. I've used test 
products so far, but for quality assurance have been trying to test with 
real products, charging to an AMEX card as well as personal VISA/Mastercard 
cards.

When I have a transaction go through, everything in my application works 
without a hitch. I'm even confirming all of the notification ids, so no 
problems there.

Throughout the process though, I have run into an issue where there is an 
inability to purchase the products.

The Market application responds to the user with a dialog with text

"Purchase canceled
Your payment could not be processed. Sign in to your Google Wallet account to 
request support."

This issue is seen on 2 Galaxy Nexus 4G devices as well as an HTC Sensation 
4G. The issue occurs on WiFi, 3G, and 4G networks. The accounts purchasing 
initially receive an "Order receipt" email, followed by an "Order 
cancellation" email. The order receipt email properly includes the full 
information for the transaction including product name, cost, order number, 
date, etc. The order cancellation also includes all of this information and 
describes the reason for cancellation as, "Took too long to deliver". The 
application gets a broadcast of a purchase state change at this time, which 
is the cancelation of the transaction.

Any insight into what's happening and why I'm having all of my transactions 
fail to complete?

It's rare that a transaction completes properly in testing.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Nikolay Elenkov]

2012/2/5 Kostya Vasilyev :
> 4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov
>  написал:
>
>
>>
>> Apparently they increased the Google
>> checkout timeout,
>> but it still happens. While this may be unavoidable,
>
>
> Unavoidable?
>
> Does the rest of the world's e-commerce suffer the same failures?

They must be :) I was referring to the answer I quoted. It says that
when credit authorization is put on hold at the credit company or carrier
(if using carrier billing) for some reason, Google checkout will eventually
time out and cancel the transaction. Quote: "It's not a bug, it's the spec".
Since it's actually out of their control, some orders will be cancelled
occasionally. The problem is that apparently it's happening rather
often for some people.

No time for a full translation right now, but this is the original thread
(in Japanese):

(some Google employees are actually nice enough to follow up on
Market issues, and report back to public forums)

https://groups.google.com/forum/?hl=ja&fromgroups#!topic/android-sdk-japan/aDNeowfQD84


>
> But that's only half the story.
>
> When this happens, some users get stuck unable to retry by placing a new
> order, with Market saying "You already have a pending order for this item".
>

I haven't seen this one for a while, too bad it's back :(.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Kostya Vasilyev]

4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov <
nikolay.elen...@gmail.com> написал:

> On Sat, Feb 4, 2012 at 7:18 AM, John Coryat  wrote:
> > Seeing that too on a couple of orders. Not a huge number though. A couple
> > today.
> >
> > Bad deal that. I also see the same users trying again and hitting the
> same
> > error.
>
> It's been said that the cause of this is payment gateways failing to
> respond
> withing the allotted time.



Interesting. It seems plausible.



> Apparently they increased the Google
> checkout timeout,
> but it still happens. While this may be unavoidable,


Unavoidable?

Does the rest of the world's e-commerce suffer the same failures?



> at least the
> message should
> be made more understandable, i.e., describing the real problem.
>
>
Yes, that'd be great if it happened - and its counterpart with regular app
purchases "Cancellation requested from phone".

Not telling users that "the seller canceled your order" would also be good,
as that'd spare me the angry emails from users asking why I took their
money and keep canceling their orders.

Can't imagine I'm the only one getting these.


How long will it take for Google support to mention this issue to the
management?

For Google product management to realize it's a real nuisance that needs to
be fixed?

For Google engineering team to change a few text literals?



But that's only half the story.

When this happens, some users get stuck unable to retry by placing a new
order, with Market saying "You already have a pending order for this item".

This last item is listed on the known issues page, so the good part is,
it's possible to refer users there -- the bad part, it's been there for a
month and a half, and the issue is much older than this.

 -- Kostya

--
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Nikolay Elenkov]

On Sat, Feb 4, 2012 at 7:18 AM, John Coryat  wrote:
> Seeing that too on a couple of orders. Not a huge number though. A couple
> today.
>
> Bad deal that. I also see the same users trying again and hitting the same
> error.

It's been said that the cause of this is payment gateways failing to respond
withing the allotted time. Apparently they increased the Google
checkout timeout,
but it still happens. While this may be unavoidable, at least the
message should
be made more understandable, i.e., describing the real problem.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[John Coryat]

Seeing that too on a couple of orders. Not a huge number though. A couple 
today.

Bad deal that. I also see the same users trying again and hitting the same 
error.

-John Coryat

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Kostya Vasilyev]

http://code.google.com/p/marketbilling/issues/detail?id=45

http://code.google.com/p/marketbilling/issues/detail?id=50 



https://groups.google.com/a/googleproductforums.com/forum/#!searchin/android-market/took$20too$20long$20to$20deliver 



-- K


On 02/02/2012 08:36 PM, Andrin von Rechenberg wrote:

I've even tried to use the sample application on:
http://developer.android.com/guide/market/billing/billing_integrate.html

But I got exactly the same error.

Anyone else seeing problems with this?

-Andrin

On Thu, Feb 2, 2012 at 3:56 PM, Andrin von Rechenberg 
mailto:andri...@gmail.com>> wrote:


Hey there

I'm trying to add in-app billing to my app.

I think i’ve implemented everything just fine,
the purchase window for an item pops up and I can click
on buy, but then it is saying “Authorizing Purchase”
for ever and then it fails. The purchase is listed
in the google checkout account as “Cancelled”
with the reason “Reason: Took too long to deliver”.
After this i receive the
com.android.vending.billing.IN_APP_NOTIFY
but the item is of course not in the state “purchased”.

This is on a Galaxy Nexus with Android 4.0.2.

Any ideas? Any help would be *really* appreciated.

Log output is ("Billing" is my log output):

D/Finsky  ( 1441): [164] MarketBillingService.getPreferredAccount:
com.miumeet.android.client: Account from first account.
D/Finsky  ( 1441): [164] MarketBillingService.getPreferredAccount:
com.miumeet.android.client: Account from first account.
I/ActivityManager(  208): START {act=android.intent.action.VIEW
cmp=com.android.vending/com.google.android.finsky.activities.IabActivity
(has extras)} from pid -1
D/Billing ( 3546): Request 463785881949596 of type
REQUEST_PURCHASE sent
I/WindowManager(  208): createSurface Window{41bc6978
com.android.vending/com.google.android.finsky.activities.IabActivity
paused=false}: DRAW NOW PENDING
W/Finsky  ( 1441): [1] CarrierParamsAction.run: Saving carrier
billing params failed.
I/ActivityManager(  208): Displayed
com.android.vending/com.google.android.finsky.activities.IabActivity:
+395ms
D/Finsky  ( 1441): [1] DfeRequest.deliverResponse: Not delivering
second response for request=[[ ]

https://android.clients.google.com/fdfe/details?doc=inapp:com.miumeet.android.client:m3
NORMAL 120]
D/Finsky  ( 1441): [1]
CarrierProvisioningAction.shouldFetchProvisioning: Required
CarrierBillingParams missing. Shouldn't fetch provisioning.
D/Finsky  ( 1441): [1] CarrierProvisioningAction.run: No need to
fetch provisioning from carrier.
D/Finsky  ( 1441): [1] PurchaseFragment.onStateChange: Finished
purchase with ID

https://android.clients.google.com/fdfe/purchaseStatus?doc=inapp:com.miumeet.android.client:m3&order=12999763169054705758.17289336772495165711.1328191047.1


D/Volley  ( 1441): [153] BasicNetwork.logSlowRequests: HTTP
response for request=<[ ]
https://android.clients.google.com/fdfe/purchaseStatus NORMAL 123>
[lifetime=47304], [size=232], [rc=200], [retryCount=0]
W/Finsky  ( 1441): [1] PurchaseInitiator.switchToError: Error when
purchasing document inapp:com.miumeet.android.client:m3:
Error{title='Purchase cancelled', docTitle='3 month premium
account', briefMessage='Review purchase with Google Wallet',
detailedMessage='Your payment could not be processed. https://checkout.google.com";>Sign in to your Google
Wallet account to request support.',
sourceUrl='details?doc=inapp:com.miumeet.android.client:m3',
detailsUrl='https://checkout.google.com'}
D/Volley  ( 1441): [1] Request.finish: 47312 ms: [ ]
https://android.clients.google.com/fdfe/purchaseStatus NORMAL 123
D/Billing ( 3546): Received com.android.vending.billing.IN_APP_NOTIFY
D/Billing ( 3546): Notification 2262237324148455585 available
D/Finsky  ( 1441): [148] MarketBillingService.getPreferredAccount:
com.miumeet.android.client: Account from first account.
D/Billing ( 3546): Request 4247658054929406474 of type
GET_PURCHASE_INFORMATION sent
D/Finsky  ( 1441): [1] MarketBillingService.sendResponseCode:
Sending response RESULT_OK for request 4247658054929406474 to
com.miumeet.android.client.
D/Billing ( 3546): Received
com.android.vending.billing.PURCHASE_STATE_CHANGED
D/Billing ( 3546): Purchase state changed


Cheers,
-Andrin


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@goo

[android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”

[Andrin von Rechenberg]

I've even tried to use the sample application on:
http://developer.android.com/guide/market/billing/billing_integrate.html

But I got exactly the same error.

Anyone else seeing problems with this?

-Andrin

On Thu, Feb 2, 2012 at 3:56 PM, Andrin von Rechenberg wrote:

> Hey there
>
> I'm trying to add in-app billing to my app.
>
> I think i’ve implemented everything just fine,
> the purchase window for an item pops up and I can click
> on buy, but then it is saying “Authorizing Purchase”
> for ever and then it fails. The purchase is listed
> in the google checkout account as “Cancelled”
> with the reason “Reason: Took too long to deliver”.
> After this i receive the
> com.android.vending.billing.IN_APP_NOTIFY
> but the item is of course not in the state “purchased”.
>
> This is on a Galaxy Nexus with Android 4.0.2.
>
> Any ideas? Any help would be *really* appreciated.
>
> Log output is ("Billing" is my log output):
>
> D/Finsky  ( 1441): [164] MarketBillingService.getPreferredAccount:
> com.miumeet.android.client: Account from first account.
> D/Finsky  ( 1441): [164] MarketBillingService.getPreferredAccount:
> com.miumeet.android.client: Account from first account.
> I/ActivityManager(  208): START {act=android.intent.action.VIEW
> cmp=com.android.vending/com.google.android.finsky.activities.IabActivity
> (has extras)} from pid -1
> D/Billing ( 3546): Request 463785881949596 of type REQUEST_PURCHASE
> sent
> I/WindowManager(  208): createSurface Window{41bc6978
> com.android.vending/com.google.android.finsky.activities.IabActivity
> paused=false}: DRAW NOW PENDING
> W/Finsky  ( 1441): [1] CarrierParamsAction.run: Saving carrier billing
> params failed.
> I/ActivityManager(  208): Displayed
> com.android.vending/com.google.android.finsky.activities.IabActivity: +395ms
> D/Finsky  ( 1441): [1] DfeRequest.deliverResponse: Not delivering second
> response for request=[[ ]
> https://android.clients.google.com/fdfe/details?doc=inapp:com.miumeet.android.client:m3NORMAL
>  120]
> D/Finsky  ( 1441): [1] CarrierProvisioningAction.shouldFetchProvisioning:
> Required CarrierBillingParams missing. Shouldn't fetch provisioning.
> D/Finsky  ( 1441): [1] CarrierProvisioningAction.run: No need to fetch
> provisioning from carrier.
> D/Finsky  ( 1441): [1] PurchaseFragment.onStateChange: Finished purchase
> with ID
> https://android.clients.google.com/fdfe/purchaseStatus?doc=inapp:com.miumeet.android.client:m3&order=12999763169054705758.17289336772495165711.1328191047.1
> D/Volley  ( 1441): [153] BasicNetwork.logSlowRequests: HTTP response for
> request=<[ ] https://android.clients.google.com/fdfe/purchaseStatusNORMAL 
> 123> [lifetime=47304], [size=232], [rc=200], [retryCount=0]
> W/Finsky  ( 1441): [1] PurchaseInitiator.switchToError: Error when
> purchasing document inapp:com.miumeet.android.client:m3:
> Error{title='Purchase cancelled', docTitle='3 month premium account',
> briefMessage='Review purchase with Google Wallet', detailedMessage='Your
> payment could not be processed. https://checkout.google.com";>Sign
> in to your Google Wallet account to request support.',
> sourceUrl='details?doc=inapp:com.miumeet.android.client:m3', detailsUrl='
> https://checkout.google.com'}
> D/Volley  ( 1441): [1] Request.finish: 47312 ms: [ ]
> https://android.clients.google.com/fdfe/purchaseStatus NORMAL 123
> D/Billing ( 3546): Received com.android.vending.billing.IN_APP_NOTIFY
> D/Billing ( 3546): Notification 2262237324148455585 available
> D/Finsky  ( 1441): [148] MarketBillingService.getPreferredAccount:
> com.miumeet.android.client: Account from first account.
> D/Billing ( 3546): Request 4247658054929406474 of type
> GET_PURCHASE_INFORMATION sent
> D/Finsky  ( 1441): [1] MarketBillingService.sendResponseCode: Sending
> response RESULT_OK for request 4247658054929406474 to
> com.miumeet.android.client.
> D/Billing ( 3546): Received
> com.android.vending.billing.PURCHASE_STATE_CHANGED
> D/Billing ( 3546): Purchase state changed
>
>
> Cheers,
> -Andrin
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing Tracking By Android Market

[Kostya Vasilyev]

On 02/01/2012 05:02 PM, beachboy wrote:

When user logs into Android Market to see the list of apps installed,
Will he see my Lite App is installed which was the original install or


Assuming you mean "when he opens the Market app on the device" - Yes.


will he see that in addition to the Lite app that he has also
purchased a license for advanced functions which is not the same as
the Paid App.

No.

Last I checked, in-app purchases were not shown in the Market app - 
unlike "regular" app purchases, which show even if the app is not installed.


-- Kostya

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Tracking By Android Market

[beachboy]

When user logs into Android Market to see the list of apps installed,
Will he see my Lite App is installed which was the original install or
will he see that in addition to the Lite app that he has also
purchased a license for advanced functions which is not the same as
the Paid App.

On Jan 31, 9:30 pm, TreKing  wrote:
> On Tue, Jan 31, 2012 at 5:49 PM, beachboy  wrote:
> > I assume then that during an uninstall and reinstall of the Lite
> > version that my app will have to check the market to see if the user
> > had previously purchased the advanced capabilities
>
> Right.
>
> > and then unlock those during the install.
>
> No. You can't do anything "during the install". You check when you run.
>
> > It still seems like the user is misinformed as to which version of the app
> > he is using from a market perspective.
>
> I don't know what you mean.
>
> --- 
> --
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Tracking By Android Market

[androidmediadeveloper]

For the reinstall check, we've used a shared preference. If
prefexists, dont check, if pref missing then check the market.

Another kludge would be to use the sqlite db version

Just my 2 cents

On Feb 1, 2:03 am, Zsolt Vasvari  wrote:
> > Which kind of defeats the purpose of trying to have a single app.
> > If you try to use IAB, you will get an error if it's not available, so
> > why block the app from the Market? I guess they are just checking
> > for the BILLING permission to filter, but still, why not let people
> > use the free app.
>
> It's clearly politics.  Why not let people from Taiwan and PRC buy
> apps in the first place?  1+ billion potential customers.  So it's
> politics.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Tracking By Android Market

[Zsolt Vasvari]

> Which kind of defeats the purpose of trying to have a single app.
> If you try to use IAB, you will get an error if it's not available, so
> why block the app from the Market? I guess they are just checking
> for the BILLING permission to filter, but still, why not let people
> use the free app.

It's clearly politics.  Why not let people from Taiwan and PRC buy
apps in the first place?  1+ billion potential customers.  So it's
politics.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing Tracking By Android Market

[Nikolay Elenkov]

On Wed, Feb 1, 2012 at 2:56 PM, Mark Carter  wrote:
>
> However, please note that non-paid app countries (e.g. China and Taiwan)
> cannot see free apps that use in-app billing.

Which kind of defeats the purpose of trying to have a single app.
If you try to use IAB, you will get an error if it's not available, so
why block the app from the Market? I guess they are just checking
for the BILLING permission to filter, but still, why not let people
use the free app.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Tracking By Android Market

[Mark Carter]

The preferred route would be to convert the paid app to use in-app billing 
and make it free. But this can only be done once the suggestion here has 
been implemented:

http://code.google.com/p/marketbilling/issues/detail?id=17#c7

Then you could ditch the free version altogether.

However, please note that non-paid app countries (e.g. China and Taiwan) 
cannot see free apps that use in-app billing.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing Tracking By Android Market

[TreKing]

On Tue, Jan 31, 2012 at 5:49 PM, beachboy  wrote:

> I assume then that during an uninstall and reinstall of the Lite
> version that my app will have to check the market to see if the user
> had previously purchased the advanced capabilities
>

Right.


> and then unlock those during the install.
>

No. You can't do anything "during the install". You check when you run.


> It still seems like the user is misinformed as to which version of the app
> he is using from a market perspective.
>

I don't know what you mean.

-
TreKing  - Chicago
transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Tracking By Android Market

[beachboy]

I assume then that during an uninstall and reinstall of the Lite
version that my app will have to check the market to see if the user
had previously purchased the advanced capabilities and then unlock
those during the install. It still seems like the user is misinformed
as to which version of the app he is using from a market perspective.




On Jan 31, 9:56 am, TreKing  wrote:
> On Tue, Jan 31, 2012 at 8:49 AM, beachboy  wrote:
> > how does the market know that I have unlocked these features and that the
> > Lite version is really now the Paid version?
>
> It doesn't - *your app* would check if the user bought the "unlock" item
> and react accordingly.
>
> --- 
> --
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing

[John Coryat]

yes

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In app billing: restore single transaction?

[xstream]

i know this is over a month old...but bump as i just found it and am having 
the same exact issue.

I have the dungeons sample working perfectly, however i want to try to add 
code to see if a certain managed item was purchased on app start 
upplease assist! thank you.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing: Creating coupons ?

[androidmediadeveloper]

Thanks for the suggestions there Kostya, we're going with a issue
refund after purchase approach in lieu of anything in the platform.

-Android Media developer

On Nov 7, 3:51 pm, Kostya Vasilyev  wrote:
> In-app billing does not allow free (of charge) items. You can refund a
> purchase once it's been completely processed (i.e. the money actually
> changed hands) and keep activation (it's up to the application code to
> treat refunded items as active: Dungeons does this).
>
> There is no expiration date either, although you could try unpublishing
> the item in the Dev Console - don't know if this affects existing
> transactions; it might. This assumes that the app does a restore
> transactions once in a while (which is subject to throttling on Google's
> side).
>
> Some similar requests for enhancements have been filed:
>
> http://code.google.com/p/marketbilling/issues/detail?id=12
>
> http://code.google.com/p/marketbilling/issues/detail?id=3
>
> ... but not specifically for coupon type functionality. You are welcome
> to do so (but I wonder if it makes any difference).
>
> At this time, I'd go with some other solution, perhaps an activator type
> application that could be installed alongside the main one, and would
> talk to your own server.
>
> -- Kostya
>
> 08.11.2011 0:38,androidmediadeveloperпишет:
>
> > We want the ability to setup a beta program for our pro app, which
> > uses in-app billing. I am exploring the possibility of giving our beta
> > testers access to the pro features on the app for free for a limited
> > amount of time, i.e., until we ship it in public. Was wondering if
> > there is a way to generate and issue something like a coupon which can
> > be redeemed by the beta tester to access the pro features. And, for us
> > as developers to have a way to put an "expiry" on the access acquired
> > via the coupon.
>
> > Thanks!
>
> --
> Kostya Vasilyev

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In app billing items

[Emanuel Moecklin]

You can't.
You have to hard code your items in the code or pull the ids from some
other place.

Cheers
Emanuel Moecklin

On Sep 26, 2:35 pm, Brad Gies  wrote:
> Hi,
>
> I'm just starting to test in app billing, and I thought there was a way to
> pull the list of available items to purchase from the market app, but I'm
> not seeing any samples etc. I do see the example of "Restoring Transactions"
> which pulls the list of previously purchased items.
>
> How do I get the list of items my user might want to purchase?
>
> Brad.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[Zsolt Vasvari]

As much as i hate hacky solutions as the next guy, if you are running
a business you must sometimes use hacks to work around bugs.  You
cannot wait around filing a bug report that may or may not be fixed in
this decade.

>
> Will try with reporting the issue, but just cannot wait till anyone
> address it. Zsolt's solution is not elegant at all, but the only quick
> one I can imagine.
>
> Thanks!
>
> On Aug 27, 8:20 am, TreKing  wrote:
>
>
>
>
>
>
>
> > On Fri, Aug 26, 2011 at 8:59 PM, groob  wrote:
> > OK, this is all I was trying to get at - the display is corrupted - that's
> > your problem. OK.
>
> > Usually a "problem" on this group is a crash or not knowing how to achieve
> > specific functionality and I was not understanding how this orientation
> > change was adversely effecting your app's functionality.
>
> > If I understand you correctly now, there is no adverse effect (your app
> > doesn't crash for example), but you don't want it to happen because it looks
> > bad to you. Correct?
>
> > Well if that's the case, I don't know. If no one else has an answer for you,
> > I'd check b.android.com and see if it's filed as a bug and if not, maybe
> > file one. Of course, I suspect this is intended behavior - the app on top is
> > what determines the current orientation and the phone can only have one
> > configuration at a time, so the top-most one takes over - I think.
>
> > P.S. - Even if your app is never intended to be used in landscape, you still
> > have to handle properly restoring your app's state, since your app will go
> > through the same cycle via other means (like pressing Home and coming back
> > to it a while later). So you may just have to bite the bullet here and
> > handle the orientation change.
>
> > --- 
> > --
> > TreKing  - Chicago
> > transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[groob]

Thank you for your interest, TreKing.

The strange thing is the display is of course rotated, but alsoscaled
down in height and untouched in width, so it looks like GL scaling has
been applied.
Nevertheless it might look like a bug or at least an unhandled
behaviour, so I need to get rid of it somehow.

The bug substance and the reason I ask a question here is that my
application is changing its orientation although I think I've done
everything what's needed to protect me against it.
To me IAB implementation is buggy and ignores this setup, not allowing
as well to handle rotations programmatically.

Will try with reporting the issue, but just cannot wait till anyone
address it. Zsolt's solution is not elegant at all, but the only quick
one I can imagine.

Thanks!


On Aug 27, 8:20 am, TreKing  wrote:
> On Fri, Aug 26, 2011 at 8:59 PM, groob  wrote:

> OK, this is all I was trying to get at - the display is corrupted - that's
> your problem. OK.
>
> Usually a "problem" on this group is a crash or not knowing how to achieve
> specific functionality and I was not understanding how this orientation
> change was adversely effecting your app's functionality.
>
> If I understand you correctly now, there is no adverse effect (your app
> doesn't crash for example), but you don't want it to happen because it looks
> bad to you. Correct?
>
> Well if that's the case, I don't know. If no one else has an answer for you,
> I'd check b.android.com and see if it's filed as a bug and if not, maybe
> file one. Of course, I suspect this is intended behavior - the app on top is
> what determines the current orientation and the phone can only have one
> configuration at a time, so the top-most one takes over - I think.
>
> P.S. - Even if your app is never intended to be used in landscape, you still
> have to handle properly restoring your app's state, since your app will go
> through the same cycle via other means (like pressing Home and coming back
> to it a while later). So you may just have to bite the bullet here and
> handle the orientation change.
>
> -
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[groob]

That's the solution we used in another title. I don't like it at all,
but nothing else can be done, as one can see.

Thank you.

On Aug 27, 8:46 am, Zsolt Vasvari  wrote:
> I would just draw a solid background of a color your choice.  I assume
> that the Checkout window takes most of the screen.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[Zsolt Vasvari]

I would just draw a solid background of a color your choice.  I assume
that the Checkout window takes most of the screen.



On Aug 27, 9:59 am, groob  wrote:
> The problem is that my application is still visible behind Google
> Checkout popup and since it has never supported landscape orientation
> (and never will be), the display is corrupted and may affect user
> experience.
>
> This may not sound like a PROBLEM for you, but it is not the matter of
> the discussion.
>
> I believe that a problem with disabling screen rotation is good enough
> to ask a question here.
>
> On Aug 26, 3:35 pm, TreKing  wrote:
>
>
>
> > On Fri, Aug 26, 2011 at 4:22 AM, groob  wrote:
> > > Although it is clearly requested, when Google Checkout window appears my
> > > manifest request is simply ignored and my game turns to landscape.
>
> > What PROBLEM is this causing for you?
>
> > ---­--
> > TreKing  - Chicago
> > transit tracking app for Android-powered devices- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing forces screen orientation change

[TreKing]

On Fri, Aug 26, 2011 at 8:59 PM, groob  wrote:

> The problem is that my application is still visible behind Google Checkout
> popup and since it has never supported landscape orientation (and never will
> be), the display is corrupted and may affect user experience.
>

OK, this is all I was trying to get at - the display is corrupted - that's
your problem. OK.

Usually a "problem" on this group is a crash or not knowing how to achieve
specific functionality and I was not understanding how this orientation
change was adversely effecting your app's functionality.

If I understand you correctly now, there is no adverse effect (your app
doesn't crash for example), but you don't want it to happen because it looks
bad to you. Correct?

Well if that's the case, I don't know. If no one else has an answer for you,
I'd check b.android.com and see if it's filed as a bug and if not, maybe
file one. Of course, I suspect this is intended behavior - the app on top is
what determines the current orientation and the phone can only have one
configuration at a time, so the top-most one takes over - I think.

P.S. - Even if your app is never intended to be used in landscape, you still
have to handle properly restoring your app's state, since your app will go
through the same cycle via other means (like pressing Home and coming back
to it a while later). So you may just have to bite the bullet here and
handle the orientation change.

-
TreKing  - Chicago
transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[groob]

The problem is that my application is still visible behind Google
Checkout popup and since it has never supported landscape orientation
(and never will be), the display is corrupted and may affect user
experience.

This may not sound like a PROBLEM for you, but it is not the matter of
the discussion.

I believe that a problem with disabling screen rotation is good enough
to ask a question here.



On Aug 26, 3:35 pm, TreKing  wrote:
> On Fri, Aug 26, 2011 at 4:22 AM, groob  wrote:
> > Although it is clearly requested, when Google Checkout window appears my
> > manifest request is simply ignored and my game turns to landscape.
>
> What PROBLEM is this causing for you?
>
> -
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing forces screen orientation change

[TreKing]

On Fri, Aug 26, 2011 at 4:22 AM, groob  wrote:

> Although it is clearly requested, when Google Checkout window appears my
> manifest request is simply ignored and my game turns to landscape.
>

What PROBLEM is this causing for you?

-
TreKing  - Chicago
transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[groob]

Imagine that my application is a game and not all games are suitable
to be displayed in both orientations.
This is why I'm forcing PORTRAIT in my manifest.

Although it is clearly requested, when Google Checkout window appears
my manifest request is simply ignored and my game turns to landscape.
I'd gladly handle the orientation change, but don't know why. The best
way IMO is to ignore it, but I find no way to achieve it.



On Aug 26, 9:06 am, Zsolt Vasvari  wrote:
> SO why does that matter?  Fix your app so it can handle the
> orientation change temporarily.  Since the Checkout it's presumably
> covering your window, it should be fairly easy to just do nothing when
> the orientation flips on you unexpectedly.
>
> On Aug 26, 2:56 pm, groob  wrote:
>
>
>
>
>
>
>
> > The problem is that my application, temporary covered by Google
> > Checkout, is changing its orientation.
> > Normally it would not react on it, keeping the display in portrait.
> > Only when billing popup appears it is happening and is definitely
> > unwanted behaviour.
>
> > On Aug 26, 1:16 am, TreKing  wrote:
>
> > > On Thu, Aug 25, 2011 at 5:37 PM, groob  
> > > wrote:
>
> > > Solution to what? You didn't state a problem.
>
> > > ---
> > >  --
> > > TreKing  - Chicago
> > > transit tracking app for Android-powered devices- Hide quoted text -
>
> > - Show quoted text -

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[Zsolt Vasvari]

SO why does that matter?  Fix your app so it can handle the
orientation change temporarily.  Since the Checkout it's presumably
covering your window, it should be fairly easy to just do nothing when
the orientation flips on you unexpectedly.



On Aug 26, 2:56 pm, groob  wrote:
> The problem is that my application, temporary covered by Google
> Checkout, is changing its orientation.
> Normally it would not react on it, keeping the display in portrait.
> Only when billing popup appears it is happening and is definitely
> unwanted behaviour.
>
> On Aug 26, 1:16 am, TreKing  wrote:
>
>
>
> > On Thu, Aug 25, 2011 at 5:37 PM, groob  wrote:
>
> > Solution to what? You didn't state a problem.
>
> > --- 
> > --
> > TreKing  - Chicago
> > transit tracking app for Android-powered devices- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing forces screen orientation change

[groob]

The problem is that my application, temporary covered by Google
Checkout, is changing its orientation.
Normally it would not react on it, keeping the display in portrait.
Only when billing popup appears it is happening and is definitely
unwanted behaviour.


On Aug 26, 1:16 am, TreKing  wrote:
> On Thu, Aug 25, 2011 at 5:37 PM, groob  wrote:
>
> Solution to what? You didn't state a problem.
>
> --- 
> --
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing broken in 3.0.27

[TheTall]

I just added a new Issue on the MarketBilling list:
http://code.google.com/p/marketbilling/issues/detail?id=39
"Star" it if you're having this problem. Add a comment if you have
more info.
-Scott

On Aug 5, 3:03 pm, Kostya Vasilyev  wrote:
> Has anyone reported this to Google?
>
> If they don't know about it (which is possible), they ain't gonna work
> on it.
>
> -- Kostya
>
> 06.08.2011 0:00, TheTall пишет:
>
>
>
>
>
>
>
>
>
> > Yes, I recently started getting this too. (3.0.27)
> > Once you get the "Took too long to deliver" message, it seems to be
> > stuck. I was just about to release an update that includes In-App
> > Billing, but ow I guess I'll wait again.
> > I Uninstalled the update for the Market, and the original version
> > doesn't get this error. I guess that's what I'll have my customer's do
> > if they run into this error.
> > -Scott Krug
>
> > On Aug 1, 9:48 am, Randall  wrote:
> >> Hello,
>
> >> I started noticing strange behavior in my own app, so I tried the
> >> "Dungeons" sample app and I'm seeing the same behavior there:
>
> >> 1. Purchase managed product
> >> 2. Observe that the order is in the un-actionable "Cancelled" state in
> >> the Checkout console (details follow)
>
> >> Jul 29     8:09 AM      Order cancelled         Google cancelled this 
> >> order.
> >> Reason: Took too long to deliver
> >> Jul 29     8:08 AM      Order received  You received a new order. Google
> >> has sent the customer an order confirmation email.
>
> >> 3. Attempting to re-purchase yields this error: "You already have a
> >> pending order for this item."
>
> >> Is anyone else seeing this behavior?  Things have been so quiet, I
> >> wonder if anyone is even using in-app billing through Google.
>
> >> Thanks,
> >> Randall
>
> --
> Kostya Vasilyev

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing broken in 3.0.27

[TheTall]

I added an issue report in MarketBilling issue list:
http://code.google.com/p/marketbilling/issues/detail?id=39
"Star" it if you are having this problem. Add comment if you have more
info.
-Scott

On Aug 5, 3:03 pm, Kostya Vasilyev  wrote:
> Has anyone reported this to Google?
>
> If they don't know about it (which is possible), they ain't gonna work
> on it.
>
> -- Kostya
>
> 06.08.2011 0:00, TheTall пишет:
>
>
>
>
>
>
>
>
>
> > Yes, I recently started getting this too. (3.0.27)
> > Once you get the "Took too long to deliver" message, it seems to be
> > stuck. I was just about to release an update that includes In-App
> > Billing, but ow I guess I'll wait again.
> > I Uninstalled the update for the Market, and the original version
> > doesn't get this error. I guess that's what I'll have my customer's do
> > if they run into this error.
> > -Scott Krug
>
> > On Aug 1, 9:48 am, Randall  wrote:
> >> Hello,
>
> >> I started noticing strange behavior in my own app, so I tried the
> >> "Dungeons" sample app and I'm seeing the same behavior there:
>
> >> 1. Purchase managed product
> >> 2. Observe that the order is in the un-actionable "Cancelled" state in
> >> the Checkout console (details follow)
>
> >> Jul 29     8:09 AM      Order cancelled         Google cancelled this 
> >> order.
> >> Reason: Took too long to deliver
> >> Jul 29     8:08 AM      Order received  You received a new order. Google
> >> has sent the customer an order confirmation email.
>
> >> 3. Attempting to re-purchase yields this error: "You already have a
> >> pending order for this item."
>
> >> Is anyone else seeing this behavior?  Things have been so quiet, I
> >> wonder if anyone is even using in-app billing through Google.
>
> >> Thanks,
> >> Randall
>
> --
> Kostya Vasilyev

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing broken in 3.0.27

[Kostya Vasilyev]

Has anyone reported this to Google?

If they don't know about it (which is possible), they ain't gonna work 
on it.


-- Kostya

06.08.2011 0:00, TheTall пишет:

Yes, I recently started getting this too. (3.0.27)
Once you get the "Took too long to deliver" message, it seems to be
stuck. I was just about to release an update that includes In-App
Billing, but ow I guess I'll wait again.
I Uninstalled the update for the Market, and the original version
doesn't get this error. I guess that's what I'll have my customer's do
if they run into this error.
-Scott Krug

On Aug 1, 9:48 am, Randall  wrote:

Hello,

I started noticing strange behavior in my own app, so I tried the
"Dungeons" sample app and I'm seeing the same behavior there:

1. Purchase managed product
2. Observe that the order is in the un-actionable "Cancelled" state in
the Checkout console (details follow)

Jul 29 8:09 AM  Order cancelled Google cancelled this order.
Reason: Took too long to deliver
Jul 29 8:08 AM  Order received  You received a new order. Google
has sent the customer an order confirmation email.

3. Attempting to re-purchase yields this error: "You already have a
pending order for this item."

Is anyone else seeing this behavior?  Things have been so quiet, I
wonder if anyone is even using in-app billing through Google.

Thanks,
Randall


--
Kostya Vasilyev

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing broken in 3.0.27

[TheTall]

Yes, I recently started getting this too. (3.0.27)
Once you get the "Took too long to deliver" message, it seems to be
stuck. I was just about to release an update that includes In-App
Billing, but ow I guess I'll wait again.
I Uninstalled the update for the Market, and the original version
doesn't get this error. I guess that's what I'll have my customer's do
if they run into this error.
-Scott Krug

On Aug 1, 9:48 am, Randall  wrote:
> Hello,
>
> I started noticing strange behavior in my own app, so I tried the
> "Dungeons" sample app and I'm seeing the same behavior there:
>
> 1. Purchase managed product
> 2. Observe that the order is in the un-actionable "Cancelled" state in
> the Checkout console (details follow)
>
> Jul 29     8:09 AM      Order cancelled         Google cancelled this order.
> Reason: Took too long to deliver
> Jul 29     8:08 AM      Order received  You received a new order. Google
> has sent the customer an order confirmation email.
>
> 3. Attempting to re-purchase yields this error: "You already have a
> pending order for this item."
>
> Is anyone else seeing this behavior?  Things have been so quiet, I
> wonder if anyone is even using in-app billing through Google.
>
> Thanks,
> Randall

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-app billing problem

[Prash Prash]

I made the changes in my app according to dungeons example. but in-app 
billing does not work.
I always receive a mail for successful transaction and transaction is 
getting charged despite of creating a test account.

I am receiving following messages.

07-21 16:56:56.542: DEBUG/vending(1035): [1] 
BaseBuyPageActivity.onPostResponse(): {PurchaseResult=OK, 
PurchaseInfo=PurchaseInfo=, SignupStatus=SIGNED_UP, TId=958405992678448, 
ShoppingCart=[ItemPrice=£1.00, 
07-21 16:57:03.792: WARN/vending(1035): [1] Util.findReceiverName(): Cannot 
find billing receiver in package 'com.myapp.test' for action: 
com.android.vending.billing.RESPONSE_CODE
07-21 16:57:28.382: WARN/vending(1035): [1] Util.findReceiverName(): Cannot 
find billing receiver in package 'com.myapp.test' for action: 
com.android.vending.billing.IN_APP_NOTIFY

in manifest.xml

  



  



can you tell me what could be wrong?

Regards,
Prashant Jain

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?

[Kostya Vasilyev]

Have you considered using the |DEVELOPER_PAYLOAD |field?

http://developer.android.com/guide/market/billing/billing_reference.html

15.07.2011 15:30, Mc Bell пишет:

On 15 июл, 14:11, Kostya Vasilyev  wrote:

The Order ID is available as well - and that doesn't change once you get
one that goes through.

But I don't have order id at the moment when I need to store my
additional information)
And I don't have additional information when I receive signedData with
orders.



--
Kostya Vasilyev

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?

[Mc Bell]

On 15 июл, 14:35, Kostya Vasilyev  wrote:
> Have you considered using the |DEVELOPER_PAYLOAD |field?

You've got a point! I didn't think about developer_payload... That
might help.
I'll try to use this.

Thanks for your advice!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?

[Mc Bell]

On 15 июл, 14:11, Kostya Vasilyev  wrote:
> The Order ID is available as well - and that doesn't change once you get
> one that goes through.

But I don't have order id at the moment when I need to store my
additional information)
And I don't have additional information when I receive signedData with
orders.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?

[Kostya Vasilyev]

The Order ID is available as well - and that doesn't change once you get 
one that goes through.


15.07.2011 15:03, Mc Bell пишет:

On 15 июл, 04:20, Nikolay Elenkov  wrote:

Use REQUEST_ID to link orders to your custom information?

Thanks for your answer.

But I don't realy understand how could I use REQUEST_ID.
As I see REQUEST_ID is unique for every new request.
I need to associate REQUEST_ID of RequestPurchase with orders.
And there is no any connectivity between this id and orders, or it
exists?



--
Kostya Vasilyev

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?

[Mc Bell]

On 15 июл, 04:20, Nikolay Elenkov  wrote:
> Use REQUEST_ID to link orders to your custom information?

Thanks for your answer.

But I don't realy understand how could I use REQUEST_ID.
As I see REQUEST_ID is unique for every new request.
I need to associate REQUEST_ID of RequestPurchase with orders.
And there is no any connectivity between this id and orders, or it
exists?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing - Alternatives to Google?

[Nikolay Elenkov]

On Wed, Jun 22, 2011 at 6:12 PM, SteveC  wrote:
> Yes PayPal is a reasonable option and can allow credit card payments
> without reqmt for the purchaser to hold a PayPal account - you will
> need to invoke PayPal api calls from a web service to setup and later
> complete the payment, the app user will need to enter their payment
> details via a WebView launched by your app.
>

IIRC, there is also an mobile payment library that launches native activities.
If you use it, you need to submit your app to PayPal for approval though.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing - Alternatives to Google?

[SteveC]

Yes PayPal is a reasonable option and can allow credit card payments
without reqmt for the purchaser to hold a PayPal account - you will
need to invoke PayPal api calls from a web service to setup and later
complete the payment, the app user will need to enter their payment
details via a WebView launched by your app.

On Jun 22, 12:13 pm, Zsolt Vasvari  wrote:
> PayPal?
>
> On Jun 22, 4:00 am, Nathan  wrote:> Can someone 
> else recommend an In app payment solution besides Google?
> > This is for digital files. Not for unlocking trials, not for unlocking
> > features of an app.
>
> > I re read my Market agreement.
>
> > I do not believe it forbids digital downloads from another payment
> > processor, such as the MP3s sold in Amazon MP3 app.
>
> > The only reason I bring this up is because In App billing is horribly
> > broken.  Google is just not a partner I would choose for payment
> > processing if there were any other choice.
>
> > The fact that 1.6 and 2.1 don't get purchase confirmations has been a
> > medium priority defect for 3 months now.
>
> > Worse, in the last week, managed purchases are getting double billed
> > and purchase state changes are not being received at all for managed
> > purchases, even with restoretransactions. Customers are angry -
> > cancellations are through the roof.
>
> >http://code.google.com/p/marketbilling/issues/detail?id=29https://cod...
>
> > Both the inability to receive purchase state broadcasts and the
> > multiple charges on managed products appear to be related to this bug,
> > from those discussions.
>
> > I've been tearing my hair out for a week or two trying to implement in
> > app billing with some help from a third party library. I blamed my own
> > code; I blamed the third party, but now it seems is at Google's end.
>
> > I don't really blame the one (1) guy that they appear to have
> > responsible for all in-app billing functionality. But maybe I should
> > go to a payment processor that is willing to fund a staff of more than
> > one person.  Any ideas?
>
> > Nathan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing - Alternatives to Google?

[Zsolt Vasvari]

PayPal?

On Jun 22, 4:00 am, Nathan  wrote:
> Can someone else recommend an In app payment solution besides Google?
> This is for digital files. Not for unlocking trials, not for unlocking
> features of an app.
>
> I re read my Market agreement.
>
> I do not believe it forbids digital downloads from another payment
> processor, such as the MP3s sold in Amazon MP3 app.
>
> The only reason I bring this up is because In App billing is horribly
> broken.  Google is just not a partner I would choose for payment
> processing if there were any other choice.
>
> The fact that 1.6 and 2.1 don't get purchase confirmations has been a
> medium priority defect for 3 months now.
>
> Worse, in the last week, managed purchases are getting double billed
> and purchase state changes are not being received at all for managed
> purchases, even with restoretransactions. Customers are angry -
> cancellations are through the roof.
>
> http://code.google.com/p/marketbilling/issues/detail?id=29https://code.google.com/p/marketbilling/issues/detail?id=32#c11
>
> Both the inability to receive purchase state broadcasts and the
> multiple charges on managed products appear to be related to this bug,
> from those discussions.
>
> I've been tearing my hair out for a week or two trying to implement in
> app billing with some help from a third party library. I blamed my own
> code; I blamed the third party, but now it seems is at Google's end.
>
> I don't really blame the one (1) guy that they appear to have
> responsible for all in-app billing functionality. But maybe I should
> go to a payment processor that is willing to fund a staff of more than
> one person.  Any ideas?
>
> Nathan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In App Billing - REQUEST_ITEM_UNAVAILABLE

[Kumar Bibek]

The App should be in daft state, but the item should be published.

*Thanks and Regards,
Kumar Bibek*
*
http://techdroid.kbeanie.com
http://www.kbeanie.com*



On Sun, Jun 19, 2011 at 12:10 AM, Conny  wrote:

> No I just saved it. I thought if I publish it the app too will be
> published. Am I missing something basic here ?
>
> On Jun 18, 11:14 pm, Kumar Bibek  wrote:
> > Have you published the item in your dev console?
> >
> > *Thanks and Regards,
> > Kumar Bibek*
> > *http://techdroid.kbeanie.comhttp://www.kbeanie.com*
> >
> >
> >
> >
> >
> >
> >
> > On Sat, Jun 18, 2011 at 11:25 PM, MCON Dev  wrote:
> > > I think I have things setup correctly, but I keep getting
> > > REQUEST_ITEM_UNAVAILABLE.
> >
> > > DDMS reports the following
> > > 06-18 21:09:27.714: DEBUG/iDHaysbert(5449): ItemName : Hello(a)
> > > SettingRingToneUri :
> > >
> android.resource://com.haysbertv2/raw/hello3timescomeonpickupthephone2.mp3
> > > PurchaseUri : hello3timescomeonpickupthephone2
> > > 06-18 21:09:27.714: DEBUG/iDHaysbert(5449): Sending Request id
> > > hello3timescomeonpickupthephone2
> > > 06-18 21:09:27.722: DEBUG/iDHaysbert(5449): RequestPurchase
> > > 06-18 21:09:27.730: DEBUG/iDHaysbert(5449): request id:
> 7697028544955964412
> > > 06-18 21:09:30.323: INFO/iDHaysbert(5449): handleCommand() action:
> > > com.android.vending.billing.RESPONSE_CODE
> > > 06-18 21:09:30.323: DEBUG/iDHaysbert(5449): Check response code
> > > RequestPurchase: RESULT_ITEM_UNAVAILABLE
> > > 06-18 21:09:30.323: DEBUG/iDHaysbert(5449): product id :
> > > hello3timescomeonpickupthephone2: RESULT_ITEM_UNAVAILABLE
> > > 06-18 21:09:30.323: INFO/iDHaysbert(5449): purchase failed
> > > 06-18 21:09:30.339: DEBUG/iDHaysbert(5449):
> > > hello3timescomeonpickupthephone2: request purchase returned
> > > RESULT_ITEM_UNAVAILABLE
> > > I have 2 email accounts (gmail). Account A is my primary account on my
> > > device and my test account on my market account. Account B is owner
> > > account on market.
> > > I have a in app product "hello3timescomeonpickupthephone2" with product
> id.
> > > All checkout file is under com.mcondev.test package and not
> > > "com.example. (from the sample).
> > > Changed the package of some Consts variables
> > > // Intent actions that we send from the BillingReceiver to the
> > > // BillingService.  Defined by this application.
> > > public static final String ACTION_CONFIRM_NOTIFICATION =
> > > "com.mcondev.test.CONFIRM_NOTIFICATION";
> > > public static final String ACTION_GET_PURCHASE_INFORMATION =
> > > "com.mcondev.test.GET_PURCHASE_INFORMATION";
> > > public static final String ACTION_RESTORE_TRANSACTIONS =
> > > "com.mcondev.test.RESTORE_TRANSACTIONS";
> > > Android Manifest has
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  android:name="com.android.vending.billing.PURCHASE_STATE_CHANGED"
> > > />
> > > 
> > > 
> >
> > > AIDL
> > > package com.android.vending.billing;
> > > import android.os.Bundle;
> > > interface IMarketBillingService {
> > >/** Given the arguments in bundle form, returns a bundle for
> results. */
> > >Bundle sendBillingRequest(in Bundle bundle);
> > > }
> >
> > > Const.java changes
> > >public static final String MARKET_BILLING_SERVICE_ACTION =
> > >"com.android.vending.billing.MarketBillingService.BIND";
> > >public static final String ACTION_CONFIRM_NOTIFICATION =
> > >"com.mcondev.test.CONFIRM_NOTIFICATION";
> > >public static final String ACTION_GET_PURCHASE_INFORMATION =
> > >"com.mcondev.test.GET_PURCHASE_INFORMATION";
> > >public static final String ACTION_RESTORE_TRANSACTIONS =
> > >"com.mcondev.test.RESTORE_TRANSACTIONS";
> >
> > > Refactored and merged Dungeons to CheckoutPurchaseObserver. Removed
> > > CATALOG code. Here are pieces of code.
> > > public CheckoutPurchaseObserver(Activity newActivity, Handler
> newHandler) {
> > >super(newActivity, newHandler);
> > >context = newActivity.getApplicationContext() ;
> > >mHandler = newHandler ;
> >
> > >mPurchaseDatabase = new PurchaseDatabase(context);
> > >mBillingService = new BillingService();
> > >mBillingService.setContext(context);
> >
> > >// Check if billing is supported.
> > >ResponseHandler.register(this);
> > >if (!mBillingService.checkBillingSupported()) {
> > >showDialog(DIALOG_CANNOT_CONNECT_ID);
> > >}
> >
> > >}
> > >   public void sendCheckoutRequest(String itemId, String quantity) {
> > >if (Consts.DEBUG)
> > >Log.d(TAG, "Sending Request id "+itemId) ;
> > >if (!mBillingService.requestPurchase(itemId, quantity))
> {
> > >showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
> > >}
> > >}
> > > . all checkoutpurchaseobserver

[android-developers] Re: In App Billing - REQUEST_ITEM_UNAVAILABLE

[Conny]

No I just saved it. I thought if I publish it the app too will be
published. Am I missing something basic here ?

On Jun 18, 11:14 pm, Kumar Bibek  wrote:
> Have you published the item in your dev console?
>
> *Thanks and Regards,
> Kumar Bibek*
> *http://techdroid.kbeanie.comhttp://www.kbeanie.com*
>
>
>
>
>
>
>
> On Sat, Jun 18, 2011 at 11:25 PM, MCON Dev  wrote:
> > I think I have things setup correctly, but I keep getting
> > REQUEST_ITEM_UNAVAILABLE.
>
> > DDMS reports the following
> > 06-18 21:09:27.714: DEBUG/iDHaysbert(5449): ItemName : Hello(a)
> > SettingRingToneUri :
> > android.resource://com.haysbertv2/raw/hello3timescomeonpickupthephone2.mp3
> > PurchaseUri : hello3timescomeonpickupthephone2
> > 06-18 21:09:27.714: DEBUG/iDHaysbert(5449): Sending Request id
> > hello3timescomeonpickupthephone2
> > 06-18 21:09:27.722: DEBUG/iDHaysbert(5449): RequestPurchase
> > 06-18 21:09:27.730: DEBUG/iDHaysbert(5449): request id: 7697028544955964412
> > 06-18 21:09:30.323: INFO/iDHaysbert(5449): handleCommand() action:
> > com.android.vending.billing.RESPONSE_CODE
> > 06-18 21:09:30.323: DEBUG/iDHaysbert(5449): Check response code
> > RequestPurchase: RESULT_ITEM_UNAVAILABLE
> > 06-18 21:09:30.323: DEBUG/iDHaysbert(5449): product id :
> > hello3timescomeonpickupthephone2: RESULT_ITEM_UNAVAILABLE
> > 06-18 21:09:30.323: INFO/iDHaysbert(5449): purchase failed
> > 06-18 21:09:30.339: DEBUG/iDHaysbert(5449):
> > hello3timescomeonpickupthephone2: request purchase returned
> > RESULT_ITEM_UNAVAILABLE
> > I have 2 email accounts (gmail). Account A is my primary account on my
> > device and my test account on my market account. Account B is owner
> > account on market.
> > I have a in app product "hello3timescomeonpickupthephone2" with product id.
> > All checkout file is under com.mcondev.test package and not
> > "com.example. (from the sample).
> > Changed the package of some Consts variables
> > // Intent actions that we send from the BillingReceiver to the
> >     // BillingService.  Defined by this application.
> >     public static final String ACTION_CONFIRM_NOTIFICATION =
> >         "com.mcondev.test.CONFIRM_NOTIFICATION";
> >     public static final String ACTION_GET_PURCHASE_INFORMATION =
> >         "com.mcondev.test.GET_PURCHASE_INFORMATION";
> >     public static final String ACTION_RESTORE_TRANSACTIONS =
> >         "com.mcondev.test.RESTORE_TRANSACTIONS";
> > Android Manifest has
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  > />
> > 
> > 
>
> > AIDL
> > package com.android.vending.billing;
> > import android.os.Bundle;
> > interface IMarketBillingService {
> >    /** Given the arguments in bundle form, returns a bundle for results. */
> >    Bundle sendBillingRequest(in Bundle bundle);
> > }
>
> > Const.java changes
> >    public static final String MARKET_BILLING_SERVICE_ACTION =
> >        "com.android.vending.billing.MarketBillingService.BIND";
> >    public static final String ACTION_CONFIRM_NOTIFICATION =
> >        "com.mcondev.test.CONFIRM_NOTIFICATION";
> >    public static final String ACTION_GET_PURCHASE_INFORMATION =
> >        "com.mcondev.test.GET_PURCHASE_INFORMATION";
> >    public static final String ACTION_RESTORE_TRANSACTIONS =
> >        "com.mcondev.test.RESTORE_TRANSACTIONS";
>
> > Refactored and merged Dungeons to CheckoutPurchaseObserver. Removed
> > CATALOG code. Here are pieces of code.
> > public CheckoutPurchaseObserver(Activity newActivity, Handler newHandler) {
> >                super(newActivity, newHandler);
> >                context = newActivity.getApplicationContext() ;
> >                mHandler = newHandler ;
>
> >                mPurchaseDatabase = new PurchaseDatabase(context);
> >                mBillingService = new BillingService();
> >                mBillingService.setContext(context);
>
> >                // Check if billing is supported.
> >                ResponseHandler.register(this);
> >                if (!mBillingService.checkBillingSupported()) {
> >                        showDialog(DIALOG_CANNOT_CONNECT_ID);
> >                }
>
> >        }
> >       public void sendCheckoutRequest(String itemId, String quantity) {
> >                if (Consts.DEBUG)
> >                        Log.d(TAG, "Sending Request id "+itemId) ;
> >                if (!mBillingService.requestPurchase(itemId, quantity)) {
> >                        showDialog(DIALOG_BILLING_NOT_SUPPORTED_ID);
> >                }
> >        }
> > . all checkoutpurchaseobserver code 
> > }
>
> > Is there anything wrong with this refactor ?
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" group.
> > To post to this group, send email to android-developers@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you ar

[android-developers] Re: in- app billing

[Mithun]

Thank you.


On May 26, 1:58 am, TreKing  wrote:
> On Tue, May 24, 2011 at 4:59 AM, Mithun  wrote:
> > 1. is it possible for me to control the pricing using 'in-app billing' ?
>
> No.
>
> >  2. once i publish the app, is it possible to change the price?
>
> Yes. Don't make it free though - then there's no going back.
>
> --- 
> --
> TreKing  - Chicago
> transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing Test failing ---- Please delete previous post

[spurwa]

Hi Joel

Can u share guide to me about how to run In-App Billing Test with SDK
or Device? Maybe you can guide me step by step for using and
running this App...
Please coz i,m newbie...:D just want to study this case for my campus
project...thanks


Regard
Spurwa

On May 25, 9:28 am, Joël Séguin  wrote:
> I just found my mistake. A dumb error: the id of my products were not
> matching...
> All is good now. Please delete or reject previous post.
>
> Joel

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-app Billing Test

[David Toledo]

from Today, is available the option In App Billing in Peru and 99 country
too. I can testing this functionality and I no appears the errors previous
in my handset
Thanks
David


2011/5/12 David Toledo 

>
> Hi All
>
> I cannot execute the app the test "dungeon test" .
>
> http://developer.android.com/intl/de/guide/market/billing/billing_testing.html#billing-testing-real
>
> Appears the following error:
> The market billing service is not available at this time. You can continue
> to use this app but you won't be able to make purchases
>
>  I have the last version from market 2.3.6 and android 2.2 my handset is
> Motorola A893, my country is Peru and my account is from the denmark, my
> account is the developer account
>
> What is the problem?
>
> Thanks
> David
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: In-App Billing example service lifecycle

[markusn82]

Good point. I did try to terminate the service manualls via
stopService after the unbind in BillingService. This seems to work in
terminating the service when the application exits, but I may be
breaking Service conventions since bound services are suppose to stop
themselves (afaik).

On Apr 20, 9:46 am, Kostya Vasilyev  wrote:
> 20.04.2011 17:32, markusn82 пишет:
>
> > I tried out several other applications with In-App billing (Dungeon
> > Defenders and Comics) and they suffered from the same issue.
>
> > Are there any official responses from the Android team about this
> > undocumented way of starting a service?
>
> If you mean this list, well, we're both here, and I don't see any, do
> you? :)
>
> Don't see any in the issue I filed, either.
>
> -- Kostya
>
>
>
>
>
>
>
>
>
> > On Apr 19, 3:51 pm, Kostya Vasilyev  wrote:
> >> Mark,
>
> >> The calls to startService in BillingService are matched by stopSelf(),
> >> so that's not the cause.
>
> >> I believe this long-running service is caused by how the purchase
> >> activity starts the billing service:
>
> >> Dungeons.java
>
> >> mBillingService = new BillingService();
> >> mBillingService.setContext(this);
>
> >> I don't see anything in the documentation to support that this is a
> >> proper way to start a service.
>
> >> Bug report:
>
> >>http://code.google.com/p/marketbilling/issues/detail?id=8
>
> >> The call to unbindService in Dungeons.onDestroy is a bit of a red herring:
>
> >> The "this" in "unbindService(this)" is BillingService.this as a
> >> ServiceConnection.
>
> >> Therefore, the code unbinds the Vending service (inside Market) from the
> >> Billing service (inside the application), releasing the former, but does
> >> nothing to stop the latter.
>
> >> -- Kostya
>
> >> 19.04.2011 22:30, markusn82 пишет:
>
> >>> Hi,
> >>> I recently implemented In-App billing for an application and I used
> >>> the Dungeons example as a starting point. I noticed that after leaving
> >>> my application (onDestroy is called in the base stack activity), the
> >>> BillingService service is still running on the phone and stays running
> >>> long after. I made sure that I was unbinding from the BillingService
> >>> service during onDestroy of my base activity.
> >>> As I understand it, a service that is started with startService needs
> >>> to be stopped with stopService/stopSelf, even if components bind/
> >>> unbind to it during its lifecycle (See
> >>>http://developer.android.com/guide/topics/fundamentals/bound-services...).
> >>> Does this mean that stopSelf should be called manually after calling
> >>> unbindService() or should the service stop itself automatically?
> >>> I looked further into the example code and saw that the BillingService
> >>> service was being started with startService, but stopService/stopSelf
> >>> was not being called ever. The call to stopSelf does exist in code but
> >>> it is never executed during the lifecycle of the application. Does
> >>> this indicate a bug in the example code or perhaps a bug in my usage.
> >>> I  noticed that the Dungeon example app itself also experiences the
> >>> same problem (service still running after application exited).
> >>> Any help would be appreciated.
> >>> Thanks,
> >>> Mark
> >> --
> >> Kostya Vasilyev --http://kmansoft.wordpress.com
>
> --
> Kostya Vasilyev --http://kmansoft.wordpress.com

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing example service lifecycle

[Jaisingh Gehlot]

2011/4/20 Kostya Vasilyev 

> 20.04.2011 17:32, markusn82 пишет:
>
>  I tried out several other applications with In-App billing (Dungeon
>> Defenders and Comics) and they suffered from the same issue.
>>
>> Are there any official responses from the Android team about this
>> undocumented way of starting a service?
>>
>
> If you mean this list, well, we're both here, and I don't see any, do you?
> :)
>
> Don't see any in the issue I filed, either.
>
> -- Kostya
>
>
>  On Apr 19, 3:51 pm, Kostya Vasilyev  wrote:
>>
>>> Mark,
>>>
>>> The calls to startService in BillingService are matched by stopSelf(),
>>> so that's not the cause.
>>>
>>> I believe this long-running service is caused by how the purchase
>>> activity starts the billing service:
>>>
>>> Dungeons.java
>>>
>>> mBillingService = new BillingService();
>>> mBillingService.setContext(this);
>>>
>>> I don't see anything in the documentation to support that this is a
>>> proper way to start a service.
>>>
>>> Bug report:
>>>
>>> http://code.google.com/p/marketbilling/issues/detail?id=8
>>>
>>> The call to unbindService in Dungeons.onDestroy is a bit of a red
>>> herring:
>>>
>>> The "this" in "unbindService(this)" is BillingService.this as a
>>> ServiceConnection.
>>>
>>> Therefore, the code unbinds the Vending service (inside Market) from the
>>> Billing service (inside the application), releasing the former, but does
>>> nothing to stop the latter.
>>>
>>> -- Kostya
>>>
>>> 19.04.2011 22:30, markusn82 пишет:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  Hi,
 I recently implemented In-App billing for an application and I used
 the Dungeons example as a starting point. I noticed that after leaving
 my application (onDestroy is called in the base stack activity), the
 BillingService service is still running on the phone and stays running
 long after. I made sure that I was unbinding from the BillingService
 service during onDestroy of my base activity.
 As I understand it, a service that is started with startService needs
 to be stopped with stopService/stopSelf, even if components bind/
 unbind to it during its lifecycle (See
 http://developer.android.com/guide/topics/fundamentals/bound-services...
 ).
 Does this mean that stopSelf should be called manually after calling
 unbindService() or should the service stop itself automatically?
 I looked further into the example code and saw that the BillingService
 service was being started with startService, but stopService/stopSelf
 was not being called ever. The call to stopSelf does exist in code but
 it is never executed during the lifecycle of the application. Does
 this indicate a bug in the example code or perhaps a bug in my usage.
 I  noticed that the Dungeon example app itself also experiences the
 same problem (service still running after application exited).
 Any help would be appreciated.
 Thanks,
 Mark

>>> --
>>> Kostya Vasilyev --http://kmansoft.wordpress.com
>>>
>>
>
> --
> Kostya Vasilyev -- http://kmansoft.wordpress.com
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
*
*
*
*
*
*
*
*
*
*
*JAI SINGH GEHLOT*
LAB. TECHNICIAN

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: In-App Billing example service lifecycle

[Kostya Vasilyev]

20.04.2011 17:32, markusn82 пишет:

I tried out several other applications with In-App billing (Dungeon
Defenders and Comics) and they suffered from the same issue.

Are there any official responses from the Android team about this
undocumented way of starting a service?


If you mean this list, well, we're both here, and I don't see any, do 
you? :)


Don't see any in the issue I filed, either.

-- Kostya


On Apr 19, 3:51 pm, Kostya Vasilyev  wrote:

Mark,

The calls to startService in BillingService are matched by stopSelf(),
so that's not the cause.

I believe this long-running service is caused by how the purchase
activity starts the billing service:

Dungeons.java

mBillingService = new BillingService();
mBillingService.setContext(this);

I don't see anything in the documentation to support that this is a
proper way to start a service.

Bug report:

http://code.google.com/p/marketbilling/issues/detail?id=8

The call to unbindService in Dungeons.onDestroy is a bit of a red herring:

The "this" in "unbindService(this)" is BillingService.this as a
ServiceConnection.

Therefore, the code unbinds the Vending service (inside Market) from the
Billing service (inside the application), releasing the former, but does
nothing to stop the latter.

-- Kostya

19.04.2011 22:30, markusn82 пишет:










Hi,
I recently implemented In-App billing for an application and I used
the Dungeons example as a starting point. I noticed that after leaving
my application (onDestroy is called in the base stack activity), the
BillingService service is still running on the phone and stays running
long after. I made sure that I was unbinding from the BillingService
service during onDestroy of my base activity.
As I understand it, a service that is started with startService needs
to be stopped with stopService/stopSelf, even if components bind/
unbind to it during its lifecycle (See
http://developer.android.com/guide/topics/fundamentals/bound-services...).
Does this mean that stopSelf should be called manually after calling
unbindService() or should the service stop itself automatically?
I looked further into the example code and saw that the BillingService
service was being started with startService, but stopService/stopSelf
was not being called ever. The call to stopSelf does exist in code but
it is never executed during the lifecycle of the application. Does
this indicate a bug in the example code or perhaps a bug in my usage.
I  noticed that the Dungeon example app itself also experiences the
same problem (service still running after application exited).
Any help would be appreciated.
Thanks,
Mark

--
Kostya Vasilyev --http://kmansoft.wordpress.com



--
Kostya Vasilyev -- http://kmansoft.wordpress.com

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en