Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Android Developers
Home
+ new post
About this group
Join this group
Message from discussion Testing In-app billing
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Thomas Bouron  
View profile  
 More options Oct 2 2012, 10:01 am
From: Thomas Bouron <tbou...@gmail.com>
Date: Tue, 2 Oct 2012 07:01:13 -0700 (PDT)
Local: Tues, Oct 2 2012 10:01 am
Subject: Re: [android-developers] Testing In-app billing
Print | View thread | Show original | Report this message | Find messages by this author

Ok, thanks for the update.

I have another related question to in-app billing. Everything works well
now but I would like to know how my product ID is managed for me (developer
account). I mean, I have only one "managed" product published, it's a
"features pack" for my application. Now, there are two scenarios:

   - For my test account, it works as expected. I can buy the "features
   pack" and as his type is managed, it's restore properly  when I
   uninstall/install again my application (through the restoreTransaction).
   - For me (ie developer account), I cannot buy the feature pack. This
   behavior is written on the documentation provided by Google but I assumed
   that the product should directly be assigned / marked as bought by Google
   Play for my me (ie developer account). It seems that it's not the case.
   Event if I uninstall/install again my application, the restoreTransaction
   returns me nothing.

So how can i set my product to "PURCHASED" state for my Developer account?

On Tuesday, October 2, 2012 1:06:26 PM UTC+2, John Coryat wrote:

> You can also cancel an order before the funds are transfered. If you do
> that, there is no "refund" to the consumer nor a credit to your account as
> the transaction never completes. This results in a purchasestate of 1 being
> sent to your server if you're using unmanaged items.

> -John Coryat

> On Tuesday, October 2, 2012 4:21:34 AM UTC-5, Thomas Bouron wrote:

>> Ok, sounds good. Thanks for the feedback.

>> On Tuesday, October 2, 2012 11:08:31 AM UTC+2, Kostya Vasilyev wrote:

>>> The "charge" button is grey, because Andorid purchased are charged
>>> automatically.

>>> "refund" will become available as the funds are actually transferred
>>> from your credit card to your developer account (two-three days, I believe).

>>> And yes, it's confusing - Google Checkout and Google Play are connected
>>> with bubble gum and glue sticks.

>>> - K

>>> 2012/10/2 Thomas Bouron <tbo...@gmail.com>

>>>> Ok so i tested my implementation successfully! That's the good news!

>>>> But i'm confused now about Google Checkout and his workflow. I can see
>>>> the payment I made with my test account. The order seems to be not shipped.
>>>> The "charge" button is grey out and when i display the order details, I
>>>> cannot charge or refund the order. Is it normal? Do i have to confirm every
>>>> order then charge it manually or can it be done automatically?

>>>> Once again, thanks for the help.

>>>> On Sunday, September 30, 2012 2:42:01 PM UTC+2, Thomas Bouron wrote:

>>>>> Thanks for the notice, i'll keep that in mind.
>>>>> I uploaded my testing version (not activated) on Google Play,
>>>>> installed it on my phone and published my product. I know that it takes
>>>>> time to be pushed over all Google servers so I'm gonna wait and start
>>>>> testing tomorrow.

>>>>> Hope everything will going fine, I'll keep this thread updated.

>>>>> Anyway, thank you all!

>>>>> On Sunday, September 30, 2012 2:06:48 PM UTC+2, John Coryat wrote:

>>>>>> The most important thing in testing is that the same version code has
>>>>>> to be uploaded to the Play store (but not activated) as you are testing
>>>>>> with. If you make changes to your test app, don't update the version code
>>>>>> or you'll have problems with in-app billing. Once you're ready to publish,
>>>>>> you'll have to update your version code before you can upload the final
>>>>>> version.

>>>>>> -John Coryat

>>>>>> On Sunday, September 30, 2012 4:15:25 AM UTC-5, Thomas Bouron wrote:

>>>>>>> Ok, i'll try that and let you know.
>>>>>>> Thanks!

>>>>>>> On Sunday, September 30, 2012 1:53:07 AM UTC+2, TreKing wrote:

>>>>>>>> On Fri, Sep 28, 2012 at 3:28 AM, Thomas Bouron <tbo...@gmail.com>wrote:

>>>>>>>>> Ok but as my app is already published, I cannot create another one
>>>>>>>>> with the same package name and save it as a draft.

>>>>>>>> Yes, you can. Upload it but don't "Activate" it, I believe.

>>>>>>>> ------------------------------**------------------------------**
>>>>>>>> ------------------------------**-------
>>>>>>>> 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-d...@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> android-developers+unsubscribe@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/android-developers?hl=en


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google