Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2017-01-06 Thread aram 
Alexandar,

Could you please let me know, how you solved this problem? Did you add any 
server layer for validating the purchase? Is it possible to validate loally 
on the device.

-
Aram
On Monday, September 30, 2013 at 1:45:55 PM UTC+5:30, Alexander Osmanov 
wrote:
>
> Thank you guys for your replies. I still have no clear understanding of 
> how to handle this problem more efficiently but at least now I am sure it's 
> not entirely myself missing something important. 
>
> Still I refuse to believe there is no one that ever faced the same problem 
> in android developers world, so I would really appreciate if someone anyone 
> described how they managed to handle it gracefully. I also have a question 
> with 100 rep bounty on SO: 
> http://stackoverflow.com/questions/18899870/android-appengine-endpoints-auth-and-inapp-billing
>  just 
> in case.
>
>
> On Mon, Sep 30, 2013 at 6:26 AM, kj  
> wrote:
>
>> I'm not saying that getting the Google account name via the API wouldn't 
>> be useful, but unfortunately that doesn't exist right now. I agree that 
>> forcing accounts is not user friendly and probably isn't a good idea for 
>> the majority of apps, but it is an option that may be considered. Sticking 
>> with the default IAB model of purchases being tied to the Google account 
>> that downloaded the app works for most cases and users have a reasonable 
>> expectation of how that will work.
>>
>> What I meant by current Google account is what Alexander mentioned 
>> previously, that the Google account making the purchase is the one that 
>> downloaded the app from the Play store.
>>
>> On Sunday, September 29, 2013 9:48:18 PM UTC-4, Nikolay Elenkov wrote:
>>
>>> On Mon, Sep 30, 2013 at 7:56 AM, kj  wrote: 
>>> > The Google IAB dialog has the Google account name that will be 
>>> associated 
>>> > with the purchase. In-app purchases are generally understood to be 
>>> tied to 
>>> > your Google account and apps you download/purchase are associated with 
>>> the 
>>> > account used in Google play. 
>>> >... 
>>> > ... If you need more explicit guaruntees of user behavior, force them 
>>> to make 
>>> > accounts. 
>>>
>>> Your point being? Letting the developer know what account the user used 
>>> to 
>>> buy an IAB item, etc. is genuinely useful. It has been requested 
>>> countless 
>>> times, but the it's not part of the API. 'Force them to make accounts' 
>>> is 
>>> hardly user friendly and is really BS in a world where people are used 
>>> to 
>>> simply using their Google/FB, etc. account. Additionally Google is 
>>> aggressively 
>>> pushing OAuth and more specifically G+ accounts for *everything* now, so 
>>> forcing people to create a bunch of throw-away accounts just to 
>>> compensate for the limitations of the IAB API is not only bad advice, it 
>>> also 
>>> goes against even Google's policy. And BTW, what exactly is 'the current 
>>> Google account'? 
>>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Android Developers" group.
>> To post to this group, send email to android-d...@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 a topic in the 
>> Google Groups "Android Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/android-developers/EbcAdThiIWc/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> android-developers+unsubscr...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Best regards, 
> AlexO 
>

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

Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2013-09-30 Thread Alexander Osmanov 
Thank you guys for your replies. I still have no clear understanding of how
to handle this problem more efficiently but at least now I am sure it's not
entirely myself missing something important.

Still I refuse to believe there is no one that ever faced the same problem
in android developers world, so I would really appreciate if someone anyone
described how they managed to handle it gracefully. I also have a question
with 100 rep bounty on SO:
http://stackoverflow.com/questions/18899870/android-appengine-endpoints-auth-and-inapp-billing
just
in case.


On Mon, Sep 30, 2013 at 6:26 AM, kj scwee...@gmail.com wrote:

 I'm not saying that getting the Google account name via the API wouldn't
 be useful, but unfortunately that doesn't exist right now. I agree that
 forcing accounts is not user friendly and probably isn't a good idea for
 the majority of apps, but it is an option that may be considered. Sticking
 with the default IAB model of purchases being tied to the Google account
 that downloaded the app works for most cases and users have a reasonable
 expectation of how that will work.

 What I meant by current Google account is what Alexander mentioned
 previously, that the Google account making the purchase is the one that
 downloaded the app from the Play store.

 On Sunday, September 29, 2013 9:48:18 PM UTC-4, Nikolay Elenkov wrote:

 On Mon, Sep 30, 2013 at 7:56 AM, kj scwe...@gmail.com wrote:
  The Google IAB dialog has the Google account name that will be
 associated
  with the purchase. In-app purchases are generally understood to be tied
 to
  your Google account and apps you download/purchase are associated with
 the
  account used in Google play.
 ...
  ... If you need more explicit guaruntees of user behavior, force them
 to make
  accounts.

 Your point being? Letting the developer know what account the user used
 to
 buy an IAB item, etc. is genuinely useful. It has been requested
 countless
 times, but the it's not part of the API. 'Force them to make accounts' is
 hardly user friendly and is really BS in a world where people are used to
 simply using their Google/FB, etc. account. Additionally Google is
 aggressively
 pushing OAuth and more specifically G+ accounts for *everything* now, so
 forcing people to create a bunch of throw-away accounts just to
 compensate for the limitations of the IAB API is not only bad advice, it
 also
 goes against even Google's policy. And BTW, what exactly is 'the current
 Google account'?

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




-- 
Best regards,
AlexO

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

Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2013-09-29 Thread Nikolay Elenkov 
On Mon, Sep 30, 2013 at 7:56 AM, kj scwee...@gmail.com wrote:
 The Google IAB dialog has the Google account name that will be associated
 with the purchase. In-app purchases are generally understood to be tied to
 your Google account and apps you download/purchase are associated with the
 account used in Google play.
...
 ... If you need more explicit guaruntees of user behavior, force them to make
 accounts.

Your point being? Letting the developer know what account the user used to
buy an IAB item, etc. is genuinely useful. It has been requested countless
times, but the it's not part of the API. 'Force them to make accounts' is
hardly user friendly and is really BS in a world where people are used to
simply using their Google/FB, etc. account. Additionally Google is aggressively
pushing OAuth and more specifically G+ accounts for *everything* now, so
forcing people to create a bunch of throw-away accounts just to
compensate for the limitations of the IAB API is not only bad advice, it also
goes against even Google's policy. And BTW, what exactly is 'the current
Google account'?

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

Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2013-09-29 Thread kj 
I'm not saying that getting the Google account name via the API wouldn't be 
useful, but unfortunately that doesn't exist right now. I agree that 
forcing accounts is not user friendly and probably isn't a good idea for 
the majority of apps, but it is an option that may be considered. Sticking 
with the default IAB model of purchases being tied to the Google account 
that downloaded the app works for most cases and users have a reasonable 
expectation of how that will work.

What I meant by current Google account is what Alexander mentioned 
previously, that the Google account making the purchase is the one that 
downloaded the app from the Play store.

On Sunday, September 29, 2013 9:48:18 PM UTC-4, Nikolay Elenkov wrote:

 On Mon, Sep 30, 2013 at 7:56 AM, kj scwe...@gmail.com javascript: 
 wrote: 
  The Google IAB dialog has the Google account name that will be 
 associated 
  with the purchase. In-app purchases are generally understood to be tied 
 to 
  your Google account and apps you download/purchase are associated with 
 the 
  account used in Google play. 
 ... 
  ... If you need more explicit guaruntees of user behavior, force them to 
 make 
  accounts. 

 Your point being? Letting the developer know what account the user used to 
 buy an IAB item, etc. is genuinely useful. It has been requested countless 
 times, but the it's not part of the API. 'Force them to make accounts' is 
 hardly user friendly and is really BS in a world where people are used to 
 simply using their Google/FB, etc. account. Additionally Google is 
 aggressively 
 pushing OAuth and more specifically G+ accounts for *everything* now, so 
 forcing people to create a bunch of throw-away accounts just to 
 compensate for the limitations of the IAB API is not only bad advice, it 
 also 
 goes against even Google's policy. And BTW, what exactly is 'the current 
 Google account'? 


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

Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2013-09-27 Thread Nikolay Elenkov 
On Sep 28, 2013 1:58 AM, Alexander Osmanov alex.osmanov...@gmail.com
wrote:

 There must be no broken in one of such important part of the API. That's
why I'd really like to hear some official recommendations for handling
this. I refuse to believe there are no apps with IAB and server side data
with accounts.


You are obviously an optimist :) Adding features to IAB takes years and the
people designing it obviously don't sell apps on Google Play. And when a
new guy takes over they re-write the whole thing from scratch...

Move on.

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

Re: [android-developers] Re: InApp Billing v3 and multiple accounts

2013-09-27 Thread Alexander Osmanov 
It's hard to just move on when you kinda spent a year writing your app and 
when the only thing left to do is to integrate it with billing :)

On Friday, September 27, 2013 10:19:05 PM UTC+4, Nikolay Elenkov wrote:


 On Sep 28, 2013 1:58 AM, Alexander Osmanov 
 alex.os...@gmail.comjavascript: 
 wrote:
 
  There must be no broken in one of such important part of the API. That's 
 why I'd really like to hear some official recommendations for handling 
 this. I refuse to believe there are no apps with IAB and server side data 
 with accounts.
 

 You are obviously an optimist :) Adding features to IAB takes years and 
 the people designing it obviously don't sell apps on Google Play. And when 
 a new guy takes over they re-write the whole thing from scratch...

 Move on.
  

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