Re: [android-developers] Re: In App Billing Error
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
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
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
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 lstipa...@gmail.com 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=enattachment: Safari.png
Re: [android-developers] Re: In App Billing Error
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 always fails with “Reason: Took too long to deliver”
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
http://stackoverflow.com/questions/10775008/in-app-billing-item-not-found/11105814#11105814 On Tue, Jun 19, 2012 at 9:37 AM, John johnj...@gmail.com 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
Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”
On Tue, Feb 14, 2012 at 15:00, John Coryat cor...@gmail.com 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
Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”
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”
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”
On Sun, Feb 5, 2012 at 2:24 AM, Nikolay Elenkov nikolay.elen...@gmail.com wrote: 2012/2/5 Kostya Vasilyev kmans...@gmail.com: 4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov nikolay.elen...@gmail.com написал: 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
Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”
On Sat, Feb 4, 2012 at 7:18 AM, John Coryat cor...@gmail.com 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”
4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov nikolay.elen...@gmail.com написал: On Sat, Feb 4, 2012 at 7:18 AM, John Coryat cor...@gmail.com 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”
2012/2/5 Kostya Vasilyev kmans...@gmail.com: 4 февраля 2012 г. 18:17 пользователь Nikolay Elenkov nikolay.elen...@gmail.com написал: 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=jafromgroups#!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”
http://code.google.com/p/marketbilling/issues/detail?id=45
http://code.google.com/p/marketbilling/issues/detail?id=50
http://code.google.com/p/marketbilling/issues/detail?id=45
https://groups.google.com/a/googleproductforums.com/forum/#!searchin/android-market/took$20too$20long$20to$20deliver
https://groups.google.com/a/googleproductforums.com/forum/#%21searchin/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
andri...@gmail.com 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:m3order=12999763169054705758.17289336772495165711.1328191047.1
https://android.clients.google.com/fdfe/purchaseStatus?doc=inapp:com.miumeet.android.client:m3order=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. a
href=https://checkout.google.com;Sign in/a 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
Re: [android-developers] Re: In-App Billing always fails with “Reason: Took too long to deliver”
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 Tracking By Android Market
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
Re: [android-developers] Re: In-App Billing Tracking By Android Market
On Tue, Jan 31, 2012 at 5:49 PM, beachboy jfma...@gmail.com 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 http://sites.google.com/site/rezmobileapps/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 Tracking By Android Market
On Wed, Feb 1, 2012 at 2:56 PM, Mark Carter mjc1...@googlemail.com 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
Re: [android-developers] Re: In-App Billing forces screen orientation change
On Fri, Aug 26, 2011 at 8:59 PM, groob krzysztof.grobe...@gmail.com 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 http://sites.google.com/site/rezmobileapps/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
On Fri, Aug 26, 2011 at 4:22 AM, groob krzysztof.grobe...@gmail.com 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 http://sites.google.com/site/rezmobileapps/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 broken in 3.0.27
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, Randallranda...@mediafriendsinc.com 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 problem
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
receiver android:name=com.myapp.test.billing.BillingReceiver
intent-filter
action android:name=com.android.vending.billing.IN_APP_NOTIFY /
action android:name=com.android.vending.billing.RESPONSE_CODE /
action
android:name=com.android.vending.billing.PURCHASE_STATE_CHANGED /
/intent-filter
/receiver
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?
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 Elenkovnikolay.elen...@gmail.com 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
Re: [android-developers] Re: In-app billing. How to store information about transactions of unmanaged products?
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 Vasilyevkmans...@gmail.com 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
Re: [android-developers] Re: In-App Billing - Alternatives to Google?
On Wed, Jun 22, 2011 at 6:12 PM, SteveC steve.g.chap...@gmail.com 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
Re: [android-developers] Re: In App Billing - REQUEST_ITEM_UNAVAILABLE
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 mcon...@gmail.com 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 coomar@gmail.com 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 mcon...@gmail.com 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
uses-permission android:name=android.permission.INTERNET /
!-- Required permission to use in-app billing. --
uses-permission android:name=com.android.vending.BILLING /
service android:name=com.mcondev.test.BillingService /
receiver android:name=com.mcondev.test.BillingReceiver
intent-filter
action android:name=com.android.vending.billing.IN_APP_NOTIFY /
action android:name=com.android.vending.billing.RESPONSE_CODE /
action
android:name=com.android.vending.billing.PURCHASE_STATE_CHANGED
/
/intent-filter
/receiver
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
Re: [android-developers] Re: In-App Billing example service lifecycle
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 Vasilyevkmans...@gmail.com 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
2011/4/20 Kostya Vasilyev kmans...@gmail.com 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 Vasilyevkmans...@gmail.com 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 as a method of activating a trial feature?
Zsolt, I filed a request for this in the market billing issue tracker yesterday: http://code.google.com/p/marketbilling/issues/detail?id=12 -- Kostya 13.04.2011 7:12, Zsolt Vasvari пишет: Well, I am not going to do that. I will just leave the feature disabled for the free version of my app. No big deal. On Apr 13, 10:26 am, Miguel Moralestherevolti...@gmail.com wrote: I thought products with 0.00 were not allowed. The same for free products. Honestly, your best bet is probably using your own server. -- 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 as a method of activating a trial feature?
http://groups.google.com/group/android-developers/msg/6f3e495456642443 Amazing it would be if they actually implemented it. There is hope though, this request for a subscription model was Accepted: http://code.google.com/p/marketbilling/issues/detail?id=3 -- Kostya 13.04.2011 12:31, Zsolt Vasvari пишет: Wow, amazing we both thought of this at the same time Thanks! On Apr 13, 4:01 pm, Kostya Vasilyevkmans...@gmail.com wrote: Zsolt, I filed a request for this in the market billing issue tracker yesterday: http://code.google.com/p/marketbilling/issues/detail?id=12 -- Kostya 13.04.2011 7:12, Zsolt Vasvari пишет: Well, I am not going to do that. I will just leave the feature disabled for the free version of my app. No big deal. On Apr 13, 10:26 am, Miguel Moralestherevolti...@gmail.com wrote: I thought products with 0.00 were not allowed. The same for free products. Honestly, your best bet is probably using your own server. -- 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 problem
Ah. Didn't know there is a bug tracker specifically for billing. I just added my data to the issue. Now, the great thing is, there are only three bugs in in-app billing: http://code.google.com/p/marketbilling/issues/list ( Ok, four. I just entered another one ) -- Kostya 11.04.2011 11:33, ishihata пишет: Hello Ivan/Kostya/Sebastian, I thought this problem is serious, so I contributed the issue to Market billing issue tracker for attention. http://code.google.com/p/marketbilling/issues/detail?id=7 I would like you to add your information here too. Thanks a lot! -- 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 problem
Hi,
Thanks for your info Ishihata, very useful. Now I am thinking more and more
that this is a market issue.
I am having the problem on a Motorola Cliq with Android 2.1-update1. I am in
the US, so I don't think it is related to the country you are testing from.
I would suggest adding your information here:
http://code.google.com/p/android/issues/detail?id=16042q=in-app%20billingcolspec=ID%20Type%20Status%20Owner%20Summary%20Stars
http://code.google.com/p/android/issues/detail?id=16042q=in-app%20billingcolspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Thanks
Seba
On Sat, Apr 9, 2011 at 2:27 AM, ishihata ishihata.k.t...@gmail.com wrote:
Hello,
I am worried of the same problem, too.
Logcat says as follows.
WARN/GTalkService(1268): [DataMsgMgr] broadcast intent callback:
result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT
cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
WARN/GTalkService(1268): TODO: implement reportNoReceiverError!
I think that this problem happens on Android 1.6 and 2.1, but does not
happen on Android 2.2.
I tried the dungeons example with some models and followings are the
result.
NG means this problem happened.
IS01 (Android 1.6) NG
IS03 (Android 2.1) NG
IS04 (Android 2.1) NG
IS05 (Android 2.2) OK
IS06 (Android 2.2) OK
Desire (Android 2.2) OK
Desire HD (Android 2.2) OK
003SH (Android 2.2) OK
005SH (Andoird 2.2) OK
Libero (Android 2.2) OK
Streak (Android 2.2) OK
Xperia (Android 2.1) NG
T-01C (Android 2.1) NG
# I am in Japan so there are many local models for Japan...
Isn't this a bug of the market app?
On Apr 9, 5:19 pm, Kostya Vasilyev kmans...@gmail.com wrote:
FWIW,
It's still not working for me - although it worked fine two or three
days ago.
Same phone, same account, same modified Dungeons sample. In fact, I made
no changes at all.
Now purchases for android.test.* are sent to Market, but never get any
response. This is as if I was running the unsigned debug build on my
test phone, but I'm running a signed release build. I even tried
removing and adding back the test account in Market profile, no change.
They are presently rolling out per-country pricing for in-app billing,
perhaps it's related.
PS - I don't see a way to set country-specific prices in my console. All
I see is USD with no way to choose another currency. Their email said
available immediately.
-- Kostya
09.04.2011 4:23, Seba ?:
Hi Ivan/Kostya,
I am having the exact same problem, and I am also seeing the same
output regarding the GTalkService.
Seba
--
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
--
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
--
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
Sebastian Ishihata,
I can also confirm this, although my sample size is much smaller:
- Moto Milestone, 2.1u1, test purchase for android.test.purchased never
completes;
Weird logcat messages:
D/vending ( 1521): [1] BaseBuyPageActivity.onOrderResponse(): state:
CART_PURCHASE response: [PurchaseResult=OK]
D/( 1521): unable to unlink
'/data/data/com.android.vending/cache/AVMC_PSU0FfaW5hcHA6b3JnLmttYW4uV2lmaU1hbmFnZXI6YW5kcm9pZC50ZXN0LnB1cmNoYXNlZA':
No such file or directory (errno=2)
D/( 1521): unable to unlink
'/data/data/com.android.vending/cache/AVMC_SU0FfaW5hcHA6b3JnLmttYW4uV2lmaU1hbmFnZXI6YW5kcm9pZC50ZXN0LnB1cmNoYXNlZA':
No such file or directory (errno=2)
followed by
W/GTalkService( 1364): [DataMsgMgr] broadcast intent callback:
result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT
cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
W/GTalkService( 1364): TODO: implement reportNoReceiverError!
- Samsung Galaxy S, 2.2, test purchase completes successfully. No weird
messages in logcat.
Needless to say, both tests are using the same .apk, release signed, etc.
-- Kostya
10.04.2011 22:28, Sebastian Pereyro ?:
Hi,
Thanks for your info Ishihata, very useful. Now I am thinking more and
more that this is a market issue.
I am having the problem on a Motorola Cliq with Android 2.1-update1. I
am in the US, so I don't think it is related to the country you are
testing from.
I would suggest adding your information here:
http://code.google.com/p/android/issues/detail?id=16042q=in-app%20billingcolspec=ID%20Type%20Status%20Owner%20Summary%20Stars
http://code.google.com/p/android/issues/detail?id=16042q=in-app%20billingcolspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Thanks
Seba
On Sat, Apr 9, 2011 at 2:27 AM, ishihata ishihata.k.t...@gmail.com
mailto:ishihata.k.t...@gmail.com wrote:
Hello,
I am worried of the same problem, too.
Logcat says as follows.
WARN/GTalkService(1268): [DataMsgMgr] broadcast intent callback:
result=CANCELLED forIntent { act=android.intent.action.REMOTE_INTENT
cat=[com.android.vending.billing.IN_APP_NOTIFY] (has extras) }
WARN/GTalkService(1268): TODO: implement reportNoReceiverError!
I think that this problem happens on Android 1.6 and 2.1, but does not
happen on Android 2.2.
I tried the dungeons example with some models and followings are the
result.
NG means this problem happened.
IS01 (Android 1.6) NG
IS03 (Android 2.1) NG
IS04 (Android 2.1) NG
IS05 (Android 2.2) OK
IS06 (Android 2.2) OK
Desire (Android 2.2) OK
Desire HD (Android 2.2) OK
003SH (Android 2.2) OK
005SH (Andoird 2.2) OK
Libero (Android 2.2) OK
Streak (Android 2.2) OK
Xperia (Android 2.1) NG
T-01C (Android 2.1) NG
# I am in Japan so there are many local models for Japan...
Isn't this a bug of the market app?
On Apr 9, 5:19 pm, Kostya Vasilyev kmans...@gmail.com
mailto:kmans...@gmail.com wrote:
FWIW,
It's still not working for me - although it worked fine two or three
days ago.
Same phone, same account, same modified Dungeons sample. In
fact, I made
no changes at all.
Now purchases for android.test.* are sent to Market, but never
get any
response. This is as if I was running the unsigned debug build on my
test phone, but I'm running a signed release build. I even tried
removing and adding back the test account in Market profile, no
change.
They are presently rolling out per-country pricing for in-app
billing,
perhaps it's related.
PS - I don't see a way to set country-specific prices in my
console. All
I see is USD with no way to choose another currency. Their email
said
available immediately.
-- Kostya
09.04.2011 4:23, Seba ?:
Hi Ivan/Kostya,
I am having the exact same problem, and I am also seeing the same
output regarding the GTalkService.
Seba
--
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
mailto:android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
mailto:android-developers%2bunsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
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
mailto:android-developers@googlegroups.com
To unsubscribe from this group, send email to
Re: [android-developers] Re: in-app billing problems
A test account lets you make purchases with your actual product ids, as a final test, before you publish the application. I don't think you can do this with any other account. 04.04.2011 13:34 пользователь Peter peter.fort...@gmail.com написал: I discovered the same. You need a production signed apk on your device to test this. I also saw that you are charged for testing this. But you can refund the money later, so that shouldn't be a problem. Actually I don't get why I need to create a test account for testing this, because everything is the same as with a non-testing-account. Or I'm I wrong her? Peter On Apr 2, 9:30 pm, Tony t...@smartmobilesolutions.com wrote: Update : after one day and a half, I am trying my code again and this time everything works :-). So I guess it is my fault to try something right after the announcement... :-) Two notes, though : 1) you need to have a real credit card assigned to your google test account (and you will be charged for real when you do the test purchases). Keep this in mind... 2) you need to deploy the production-signed apk on the test device, when you test against themarket. So export a production signedversionfrom Eclipse, upload it as a draft on theMarket, create/ modify your in-apps items on themarket, publish them. Then deploy the same apk on the test device with test google account and do the testing. Anyway, it's fine now. Guys, thanks for the comments and good luck :-) -- 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 problems
Billing testing works fine on my G1 using 1.6 On Thu, Mar 31, 2011 at 1:30 PM, Mr Pants pantssoftw...@googlemail.comwrote: Hi Tony, Thanks for pointing that out, will save me wasting even more time on getting this very clunky functionality workingI'm sure it could have been made easier. I'm sure the original release said it was available for any device (1.6+) with the right version of Android Market. Cheers On Mar 31, 4:14 pm, Tony t...@smartmobilesolutions.com wrote: Hi guys, 1) Google announced yesterday that the in-app billing is officially available. However, seems I am still getting RESULT_BILLING_UNAVAILABLE with Market 2.3.4 Then I looked athttp:// market.android.com/support/bin/answer.py?answer=1050566 It stated that at this time it is available only on Android 3.0 devices with MyApps 5.0.12 or higher. (This statement is only there). NIce. Does anyone has other results with 2.3.4 or eventually has some information when we can use in-app purchase for 2.3.4? 2) On 3.0 / MyApps 5.0.12, my test implementation of in-app purchase works fine with the reserved product IDs for testing static in-app billing responses. Here is the test environment : - I have uploaded draft apk with uses-permission android:name=com.android.vending.BILLING /, signed for production (not debug) - The previous version of the app is published - I created in-app items for the app and their status is published - I created a test google user - the testing tablet is reset and booted up with the same test google account as primary google account So if the sku inside in the app is one of the reserved ids (like android.test.purchased ), everything is fine. If I change only the sku to one of mine in-app items ids, and try the purchase, the market is showing the following message window : Application Error : This version of the application is not configured for Market Billing. Check the help center for more information. There is nothing special in the log : BillingService RequestPurchase BillingService request id: 5088870391717748441 mPayloadcontents null I double checked the public key. Does anone has a better luck with that? Thanks! -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/ http://www.youtube.com/user/revoltingx -- 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 problems
Well, I'm saying that the market service returns RESULT_BILLING_OK (or whatever) on my G1. Perhaps it's a problem with your implementation, or version. But it certainly doesn't just work on 3.0+ devices. On Thu, Mar 31, 2011 at 1:55 PM, Mr Pants pantssoftw...@googlemail.comwrote: Testing yes, real in-app products? On Mar 31, 9:35 pm, Miguel Morales therevolti...@gmail.com wrote: Billing testing works fine on my G1 using 1.6 On Thu, Mar 31, 2011 at 1:30 PM, Mr Pants pantssoftw...@googlemail.com wrote: Hi Tony, Thanks for pointing that out, will save me wasting even more time on getting this very clunky functionality workingI'm sure it could have been made easier. I'm sure the original release said it was available for any device (1.6+) with the right version of Android Market. Cheers On Mar 31, 4:14 pm, Tony t...@smartmobilesolutions.com wrote: Hi guys, 1) Google announced yesterday that the in-app billing is officially available. However, seems I am still getting RESULT_BILLING_UNAVAILABLE with Market 2.3.4 Then I looked athttp:// market.android.com/support/bin/answer.py?answer=1050566 It stated that at this time it is available only on Android 3.0 devices with MyApps 5.0.12 or higher. (This statement is only there). NIce. Does anyone has other results with 2.3.4 or eventually has some information when we can use in-app purchase for 2.3.4? 2) On 3.0 / MyApps 5.0.12, my test implementation of in-app purchase works fine with the reserved product IDs for testing static in-app billing responses. Here is the test environment : - I have uploaded draft apk with uses-permission android:name=com.android.vending.BILLING /, signed for production (not debug) - The previous version of the app is published - I created in-app items for the app and their status is published - I created a test google user - the testing tablet is reset and booted up with the same test google account as primary google account So if the sku inside in the app is one of the reserved ids (like android.test.purchased ), everything is fine. If I change only the sku to one of mine in-app items ids, and try the purchase, the market is showing the following message window : Application Error : This version of the application is not configured for Market Billing. Check the help center for more information. There is nothing special in the log : BillingService RequestPurchase BillingService request id: 5088870391717748441 mPayloadcontents null I double checked the public key. Does anone has a better luck with that? Thanks! -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/http://www.youtube.com/user/revoltingx -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/ http://www.youtube.com/user/revoltingx -- 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 problems
Either that, or I have a special G1. I'm guessing they'll support lower versions sooner rather later. On Thu, Mar 31, 2011 at 2:02 PM, Miguel Morales therevolti...@gmail.comwrote: Well, I'm saying that the market service returns RESULT_BILLING_OK (or whatever) on my G1. Perhaps it's a problem with your implementation, or version. But it certainly doesn't just work on 3.0+ devices. On Thu, Mar 31, 2011 at 1:55 PM, Mr Pants pantssoftw...@googlemail.comwrote: Testing yes, real in-app products? On Mar 31, 9:35 pm, Miguel Morales therevolti...@gmail.com wrote: Billing testing works fine on my G1 using 1.6 On Thu, Mar 31, 2011 at 1:30 PM, Mr Pants pantssoftw...@googlemail.com wrote: Hi Tony, Thanks for pointing that out, will save me wasting even more time on getting this very clunky functionality workingI'm sure it could have been made easier. I'm sure the original release said it was available for any device (1.6+) with the right version of Android Market. Cheers On Mar 31, 4:14 pm, Tony t...@smartmobilesolutions.com wrote: Hi guys, 1) Google announced yesterday that the in-app billing is officially available. However, seems I am still getting RESULT_BILLING_UNAVAILABLE with Market 2.3.4 Then I looked athttp:// market.android.com/support/bin/answer.py?answer=1050566 It stated that at this time it is available only on Android 3.0 devices with MyApps 5.0.12 or higher. (This statement is only there). NIce. Does anyone has other results with 2.3.4 or eventually has some information when we can use in-app purchase for 2.3.4? 2) On 3.0 / MyApps 5.0.12, my test implementation of in-app purchase works fine with the reserved product IDs for testing static in-app billing responses. Here is the test environment : - I have uploaded draft apk with uses-permission android:name=com.android.vending.BILLING /, signed for production (not debug) - The previous version of the app is published - I created in-app items for the app and their status is published - I created a test google user - the testing tablet is reset and booted up with the same test google account as primary google account So if the sku inside in the app is one of the reserved ids (like android.test.purchased ), everything is fine. If I change only the sku to one of mine in-app items ids, and try the purchase, the market is showing the following message window : Application Error : This version of the application is not configured for Market Billing. Check the help center for more information. There is nothing special in the log : BillingService RequestPurchase BillingService request id: 5088870391717748441 mPayloadcontents null I double checked the public key. Does anone has a better luck with that? Thanks! -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/http://www.youtube.com/user/revoltingx -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/ http://www.youtube.com/user/revoltingx -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://solrpg.com/ http://www.youtube.com/user/revoltingx -- 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 problems
Fyi, I'm testing it using the dungeons sample app google provides. You should try that first and save some time On Mar 31, 2011 2:30 PM, Mr Pants pantssoftw...@googlemail.com wrote: It wouldn't surprise me, if my problems were down to my implementation :) I guess another few hours wouldn't hurt On Mar 31, 10:06 pm, Miguel Morales therevolti...@gmail.com wrote: Either that, or I have a spe... On Thu, Mar 31, 2011 at 2:02 PM, Miguel Morales therevolti...@gmail.com wrote: Well, I'm saying that the market service returns RESULT_BILLING_OK (or wha... On Thu, Mar 31, 2011 at 1:55 PM, Mr Pants pantssoftw...@googlemail.com wrote: Testing yes, real in-app products? On Mar 31, 9:35 pm, Miguel Morales therevolti...@g... -- You received this message because you are subscribed to the Google Groups Android Developers group... -- 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 does not work - although everything has been checked
26.03.2011 15:25, Marc Reichelt пишет: Hi Kostya, did you publish the In-app-items? Testing In-app payment will not work if you do not publish the In-app-items. You don't have to publish your app for testing it. In fact, you can not publish an application using In-app billing right now. Ah. Good point, thanks. Just published my test item, and tried to purchase it from the development phone. It short, it worked. However, even though my development phone is listed as a test account in the Developer Console profile, I still had to enter a real credit card number (no VISA--FAKE there), and they charged my card for real. Good thing I set the price to $0.99. After I submitted the purchase, the Checkout window didn't go away for a long time, then I got an error report in the logcat about the billing activity having leaked a window. A couple of minutes later the application showed that the item state changed to PURCHASED. Oh, I am using the actual release build, signed with a non-debug key, same .apk as I uploaded to Market. Are you perhaps using a debug build on your phone? -- Kostya My problem just is that I did everything the documentation says and still can not test it successfully. -- 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 does not work - although everything has been checked
26.03.2011 15:57, Marc Reichelt пишет: Hi Kostya, of course they did charge your account for real Why the of course? I set this phone up as a test account in the Market console, and the system knows this. - you_definitely_ should read the In-app documentation before doing anything Yes, definitely plan to, when I actually start implementing it in my app. So far I've only had time for a first, cursory read. Anyway, it was only $0.99, less than half the price of a pack of cigarettes. And I can issue a refund to myself. And as I pointed out I am using a correctly signed release build, not the debug build. Still having problems. Weird. From your description, we have identical setups: release builds uploaded but not published, installed on the phone, item published in the console, Market 2.3.4. And yet it worked for me and didn't work for you. -- Kostya Regards Marc Reichelt ||http://www.marcreichelt.de/ -- 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 and trial period
String, Doug, kernelpanic - thank you for your responses. Indeed, the option with lite/pro LVL looks most reasonable to me at this point. What I was really hoping for is that I'd missed something in the in-app billing documentation, and it's possible to use it for trial period checks. Especially since it would be really easy for Google to implement, as a special item type (in addition to the current managed / unmanaged ones), where a transaction goes through and is maintained by the server, but the customer is not charged anything. It would also be possible to do this without a special purchase type, by having a zero-price item, except the docs specifically prohibit that. Oh well. I'll look into writing a dungeon game, with healing potions for sale :) Thanks, -- Kostya 23.02.2011 1:32, Doug пишет: I've been doing lite/paid versions since the market first accepted paid apps and it's worked well. The downside is that the people who go paid then uninstall the lite, which presumably hurts its ranking. You could try getting around that by implementing an unlocker app as the paid version so the user has to retain both in order to get the full benefits. The downside to that might be reduced ratings/reviews for the paid unlocker, which could hurt its ranking. Doug -- 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...
I have tried to implement code using the provided example project. Although you can get some work done, the lack of a 2.3 market version really hurts testing. I have tried running the Dungeon app on a 1.6 device with no luck. On Sat, Feb 5, 2011 at 2:14 PM, fooyee reloadingthej...@gmail.com wrote: switching gears a bit, has anyone tried out the in-app billing (dungeon.java) sample provided by Google? Is it working OK? On Feb 5, 9:47 pm, Justin Giles jtgi...@gmail.com wrote: Ok, you two. Now I'm hungry for a donut while I'm doing my laundry! On Sat, Feb 5, 2011 at 10:10 AM, Kostya Vasilyev kmans...@gmail.com wrote: 05.02.2011 18:59, Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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.comandroid-developers%2Bunsubs cr...@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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx -- 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...
So one thing I haven't found yet.. is in-app only for 2.3 and later apps? Or is the SDK going to work for 2.0+? Given that 2.1 and 2.2 are the majority market, with 2.3 going to be building up this year, I am fine with it targeting that, but if it's 2.3 and later, that kinda sucks because it will be a while before we can really tap into a larger market of 2.3+ devices. On Sat, Feb 12, 2011 at 1:54 AM, Miguel Morales therevolti...@gmail.comwrote: I have tried to implement code using the provided example project. Although you can get some work done, the lack of a 2.3 market version really hurts testing. I have tried running the Dungeon app on a 1.6 device with no luck. On Sat, Feb 5, 2011 at 2:14 PM, fooyee reloadingthej...@gmail.com wrote: switching gears a bit, has anyone tried out the in-app billing (dungeon.java) sample provided by Google? Is it working OK? On Feb 5, 9:47 pm, Justin Giles jtgi...@gmail.com wrote: Ok, you two. Now I'm hungry for a donut while I'm doing my laundry! On Sat, Feb 5, 2011 at 10:10 AM, Kostya Vasilyev kmans...@gmail.com wrote: 05.02.2011 18:59, Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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.comandroid-developers%2Bunsubs cr...@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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx -- 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...
This: http://developer.android.com/guide/market/billing/billing_about.html says: In-app billing relies on version 2.3.0 (and higher) of the Android Market application, which may not be available yet. and doesn't say anything about the platform version. -- Kostya 12.02.2011 21:56, Kevin Duffey пишет: So one thing I haven't found yet.. is in-app only for 2.3 and later apps? Or is the SDK going to work for 2.0+? Given that 2.1 and 2.2 are the majority market, with 2.3 going to be building up this year, I am fine with it targeting that, but if it's 2.3 and later, that kinda sucks because it will be a while before we can really tap into a larger market of 2.3+ devices. On Sat, Feb 12, 2011 at 1:54 AM, Miguel Morales therevolti...@gmail.com mailto:therevolti...@gmail.com wrote: I have tried to implement code using the provided example project. Although you can get some work done, the lack of a 2.3 market version really hurts testing. I have tried running the Dungeon app on a 1.6 device with no luck. On Sat, Feb 5, 2011 at 2:14 PM, fooyee reloadingthej...@gmail.com mailto:reloadingthej...@gmail.com wrote: switching gears a bit, has anyone tried out the in-app billing (dungeon.java) sample provided by Google? Is it working OK? On Feb 5, 9:47 pm, Justin Giles jtgi...@gmail.com mailto:jtgi...@gmail.com wrote: Ok, you two. Now I'm hungry for a donut while I'm doing my laundry! On Sat, Feb 5, 2011 at 10:10 AM, Kostya Vasilyev kmans...@gmail.com mailto:kmans...@gmail.com wrote: 05.02.2011 18:59, Maps.Huge.Info http://Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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 mailto:android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com mailto:android-developers%2bunsubscr...@googlegroups.comandroid-developers%2Bunsubs cr...@googlegroups.com mailto:cr...@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 mailto:android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com mailto:android-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx -- 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 mailto:android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com mailto:android-developers%2bunsubscr...@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
Re: [android-developers] Re: In app billing...
According to the docs, it's going to be for 1.6+ devices. They will be pushing updates to the market app worldwide at some point. It's not really an SDK. It's an aidl file which you use to communicate with the market app. But with no 2.3.0 version of the market app available yet, it's not possible to fully test it yet. Even the dungeon app won't work as far as I can tell. On Sat, Feb 12, 2011 at 11:14 AM, Kostya Vasilyev kmans...@gmail.com wrote: This: http://developer.android.com/guide/market/billing/billing_about.html says: In-app billing relies on version 2.3.0 (and higher) of the Android Market application, which may not be available yet. and doesn't say anything about the platform version. -- Kostya 12.02.2011 21:56, Kevin Duffey пишет: So one thing I haven't found yet.. is in-app only for 2.3 and later apps? Or is the SDK going to work for 2.0+? Given that 2.1 and 2.2 are the majority market, with 2.3 going to be building up this year, I am fine with it targeting that, but if it's 2.3 and later, that kinda sucks because it will be a while before we can really tap into a larger market of 2.3+ devices. On Sat, Feb 12, 2011 at 1:54 AM, Miguel Morales therevolti...@gmail.com wrote: I have tried to implement code using the provided example project. Although you can get some work done, the lack of a 2.3 market version really hurts testing. I have tried running the Dungeon app on a 1.6 device with no luck. On Sat, Feb 5, 2011 at 2:14 PM, fooyee reloadingthej...@gmail.com wrote: switching gears a bit, has anyone tried out the in-app billing (dungeon.java) sample provided by Google? Is it working OK? On Feb 5, 9:47 pm, Justin Giles jtgi...@gmail.com wrote: Ok, you two. Now I'm hungry for a donut while I'm doing my laundry! On Sat, Feb 5, 2011 at 10:10 AM, Kostya Vasilyev kmans...@gmail.com wrote: 05.02.2011 18:59, Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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.comandroid-developers%2Bunsubs cr...@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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx -- 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 -- Kostya Vasilyev -- http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups
Re: [android-developers] Re: In app billing...
05.02.2011 18:59, Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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...
That's interesting. Thanks for the info. 05.02.2011 20:33, Maps.Huge.Info (Maps API Guru) пишет: It's the right to use the software in a certain way, to repeatedly... In my business, I have a stated policy of No refunds under any circumstances. I've had this policy for over 30 years and it has served me well. I have the policy stated in several places and so far, it hasn't been a problem. If you state this clearly then it shouldn't be an issue with the consumers. Sure, you may scare away a few by having this policy but the end result is less complaining and customers who are more likely to be satisfied. I see no reason to change this policy with apps. Besides, we're talking a couple of dollars per transaction. It's not like they're choosing between buying your $2 item or paying their rent. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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...
So I have a few thoughts on this subject. I have been hoping ever since apple introduced this feature for iPhone/iPad that Google would hurry up and add this. I know of several developers that are making a huge sum more with in-app virtual good purchases than their pro version ever sold. Because it's so tightly integrated in the app, it's a very simple dialog to ok/cancel the purchase and you keep using the app. I have not read the docs yet, I am going to assume that this is the same experience android users will see... they won't be taken out of the app to approve the payment correct? To me, this is the holy grail of mobile apps for developers. I happen to know of a few people in the micro transaction business, and the predictions for this particular segment is astronomical. Tapping in to it therefore is just a matter of finding that right use of it for any given app. Games obviously are going to be the big winner with this feature, as virtual goods, map packs and so forth are unmatched in consumption by end users. I am blown away with how easy it is for someone to spend a buck to customize their avatar look, or a buck for a avatar item.. few bucks to customize, etc etc. I am really hoping.. and if anyone has read and has a clear understanding of what is going to possible.. that they have at least provided what apple has in their API for both end users and developers. Apple for example shows the top in-app purchases. Is there a way for the developer to get info on each and every in-app purchase, to figure out what is selling good and what might not be? Will the Market display the top in-app purchases? For the end user.. how does the in-app purchase go.. is it simply a dialog to approve/deny the purchase? What if they have never bought anything yet? I see that Google and ATT now allow for purchases to appear on their bill. I am hoping at least for ATT that in-app purchases automatically go to their bill as well? Is there any time frame on when Verizon, t-mobile, sprint and other carriers around the world will support this? On Sat, Feb 5, 2011 at 9:33 AM, Maps.Huge.Info (Maps API Guru) cor...@gmail.com wrote: It's the right to use the software in a certain way, to repeatedly... In my business, I have a stated policy of No refunds under any circumstances. I've had this policy for over 30 years and it has served me well. I have the policy stated in several places and so far, it hasn't been a problem. If you state this clearly then it shouldn't be an issue with the consumers. Sure, you may scare away a few by having this policy but the end result is less complaining and customers who are more likely to be satisfied. I see no reason to change this policy with apps. Besides, we're talking a couple of dollars per transaction. It's not like they're choosing between buying your $2 item or paying their rent. -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.comandroid-developers%2bunsubscr...@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...
Ok, you two. Now I'm hungry for a donut while I'm doing my laundry! On Sat, Feb 5, 2011 at 10:10 AM, Kostya Vasilyev kmans...@gmail.com wrote: 05.02.2011 18:59, Maps.Huge.Info (Maps API Guru) пишет: I believe being able to provide refunds is important. When you go to a real-world store Since a user upgrading to a pro version isn't buying anything tangible, it's more like going into a donut shop, buying a donut and eating it. How many consumers ask for refunds at that point? Under some circumstances, a refund is called for but not in the same way as a consumer returning an unopened package that can be resold. That's a different type of product, more like a health potion in an RPG game. You might call it a virtual consumable. To me, issuing a refund for a software product is only to be done under some unusual circumstance not because of buyer remorse. The donut has been eaten and that's that. For a virtual consumable, yes. But I'm talking specifically about upgrading from lite to pro, which is not a consumable at all. It's the right to use the software in a certain way, to repeatedly perform certain tasks, and is more like buying... hmm... a microwave or a washing machine, not a donut. -John Coryat -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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.comandroid-developers%2bunsubscr...@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...
Completely agree John if we can use it as Dianne suggested...:) I don't mind doing a bunch of the work myself to manage it (kind of prefer it). Sincerely, Brad Gies --- Bistro Bot - Bistro Blurb http://bgies.comhttp://nocrappyapps.com http://bistroblurb.com http://forcethetruth.com http://ihottonight.com --- Everything in moderation, including abstinence (paraphrased) Every person is born with a brain... Those who use it well are the successful happy ones - Brad Gies Adversity can make or break you... It's your choice... Choose wisely - Brad Gies Never doubt that a small group of thoughtful, committed people can change the world. Indeed. It is the only thing that ever has - Margaret Mead On 04/02/2011 3:06 PM, Maps.Huge.Info (Maps API Guru) wrote: Personally, I think the unmanaged in-app purchase would be ideal for a subscription service for my app. I'll have to do a lot of work to get this going but I'll finally have something to offer the nearly 800,000 users who have my app on their device. Sure, there are going to be pitfalls and also bugs but I see this as very positive development for Android. -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...
On Fri, Feb 4, 2011 at 2:17 PM, Nathan critter...@crittermap.com wrote: Right now, I just wouldn't want to rock the boat so much. My paid app can be found without , people can still find the DEMO under related apps. The DEMO has never been anywhere close to the top where people can find it. Some people have installed it at position 265. The paid app has 0.5 extra points in ratings. That makes sense, most people who like the app will be reviewing the paid app instead. So perhaps I'll save the in-app purchases thing for premium content. And only make it available in a paid app, since those people have proven that they will pay something and can deal with Google Checkout. How about this: for existing apps, keep the separate paid vs. trial versions as you do now. Just change things so that the trial version has in-app purchase to turn it into a full app. Do your paid app is the same as the trial version, it just knows that it is already unlocked. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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...
I asked this question earlier but I think it got buried... Why is it not possible to access all licensing information (whether full app purchases, or in-app purchases) through a single API? This would make converting a Pro app to an Free-with-in-app-upgrade app relatively trivial. -- 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...
On Fri, Feb 4, 2011 at 5:55 PM, Mark Carter mjc1...@googlemail.com wrote: Why is it not possible to access all licensing information (whether full app purchases, or in-app purchases) through a single API? This would make converting a Pro app to an Free-with-in-app-upgrade app relatively trivial. Well a free app and a paid app are completely different and independent entities, so I imagine the basic problem is that they don't have any association or any way to know about each other. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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...
IIRC a Paid app can be converted to a Free app by simply changing the price to 0? 1. I'm looking for a way to convert my Pro app to support in-app purchases. In the long run I want to use the free app with in-app upgrade model and I don't want to leave my pro users behind (i.e. I'd rather drop the existing Lite app). 2. The *free app and paid app being completely independent entities* is another problem. Devs should be able to specify This is the pro app of that lite app. Making this declaration opens up all sorts of possibilities. Sharing in-app purchases might be one. How the Market displays the two might be another. The Pro/Lite model is a hack devs have used for lack of a better alternative. For some, the in-app-upgrade model is a better alternative. For others, the Pro/Lite model is still the best because they want a build (Lite) which does not include pro-only code (and don't want to go down the messy route of downloading pro jars). Anyway, that second point is not as important as the first: i.e. how to achieve smooth transition from paid-app to free-app-with-in-app-upgrade? On 5 February 2011 11:12, Dianne Hackborn hack...@android.com wrote: On Fri, Feb 4, 2011 at 5:55 PM, Mark Carter mjc1...@googlemail.comwrote: Why is it not possible to access all licensing information (whether full app purchases, or in-app purchases) through a single API? This would make converting a Pro app to an Free-with-in-app-upgrade app relatively trivial. Well a free app and a paid app are completely different and independent entities, so I imagine the basic problem is that they don't have any association or any way to know about each other. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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.comandroid-developers%2bunsubscr...@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...
Sorry I can't address plans on Market, that's not what I work on. On Wed, Feb 2, 2011 at 6:54 PM, William Ferguson william.ferguson.au@ gmail.com wrote: Yep. Just wish that as well as the Managed and Unmanaged Purchase Types there was also Managed-Periodic that supported limited lifetime purchases (ie subscriptions). Yes I know its possible to implement this using Unmanaged and having your own server to track the subscription. But its clumsy, fragile, easily subverted and requires quite a bit of extra work for each developer for what looks like a very common use case. A subscription service means that there is an incentive to continually improve your app for your existing users. And honestly, getting them to part with $1/year sounds like a reasonable proposition for a well maintained app. Dianne, is there any movement in that direction that you are aware of? On Feb 3, 12:25 pm, Dianne Hackborn hack...@android.com wrote: How about using it to be able to put your app up on market as a free trial version, using in-app billing to unlock the full version? On Wed, Feb 2, 2011 at 5:54 PM, Damien Cooke cooke.dam...@gmail.com wrote: Mainly for apps where buying extra services makes sense. Like a magazine application that allows you to buy and download magazine subscriptions or editions within the app. Damien sent from my HTC Desire On 03/02/2011 11:39 AM, sblantipodi perini.dav...@dpsoftware.org wrote: Hi, I just received a mail from google that informs me that In-App Billing will be available soon. Can you explain me please what is the in app billing and what is used for? We can create buy now button now without any additional apis that redirect customers to the market, why use in app billing on android? -- 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.comandroid-developers%2bunsubscr...@googlegroups.com android-developers%2bunsubscr...@googlegroups.comandroid-developers%252bunsubscr...@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.comandroid-developers%2bunsubscr...@googlegroups.com android-developers%2bunsubscr...@googlegroups.comandroid-developers%252bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
