InApp Billing same account multiple devices

by keianhzo » Mon, 16 May 2011 19:19:16 GMT


Sponsored Links
 Hi,

We are testing InApp billing to include in one of our apps to buy the
ads removal. At the moment the main issue we have is that if you have
two devices with the same account and the app installed you are
supposed to get all the InApp billing notifications in both the
devices but is not working that way for me. It sometimes sends
notifications to both devices and sometimes just to one of them. This
is problematic because as stated in the sample code and in some InApp
billing issues, you are only supposed to restore the transactions when
the app is first started, but you can't rely in the InApp billing
notification system because sometimes notifications fail, so you end
up with inconsistencies with the purchased items in devices using the
same google account.
Is this a known issue?, anyone experiencing similar problems?. Any
solution?.

Thanks.

-- 



Re: InApp Billing same account multiple devices

by keianhzo » Thu, 19 May 2011 17:56:04 GMT


 Anyone on this?. I think is quite an important subject. The billing
system is failing in such a basic thing as sending notifications.
Maybe I should place an issue in the marketbilling issues list.




-- 


Sponsored Links


Re: Re: InApp Billing same account multiple devices

by Kostya Vasilyev » Thu, 19 May 2011 18:14:42 GMT


 There is already an open issue for lost notifications:

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

however, it does not specifically concern multi-device setup.

I've provided a list of order numbers for this issue, and got logs from 
the Market team showing that the notifications for those orders were 
received and confirmed by my application within seconds (the users never 
saw the confirmation, hence the list).


I don't see how my code could confirm a purchase and not activate it for 
the user, the Market team obviously trusts their logs, and that's where 
it is at for me now.


If you have specific order numbers, you can post them in the bug report.

-- Kostya

19.05.2011 13:55, keianhzo :
Anyone on this?. I think is quite an important subject. The billing system is failing in such a basic thing as sending notifications. Maybe I should place an issue in the marketbilling issues list.
Hi, We are testingInAppbilling to include in one of our apps to buy the ads removal. At the moment the main issue we have is that if you have two devices with the same account and the app installed you are supposed to get all theInAppbilling notifications in both the devices but is not working that way for me. It sometimes sends notifications to both devices and sometimes just to one of them. This is problematic because as stated in the sample code and in someInApp billing issues, you are only supposed to restore the transactions when the app is first started, but you can't rely in theInAppbilling notification system because sometimes notifications fail, so you end up with inconsistencies with the purchased items in devices using the same google account. Is this a known issue?, anyone experiencing similar problems?. Any solution?. Thanks.
-- Kostya Vasilyev -- http://kmansoft.wordpress.com --



Other Threads

1. in API Demo ,Alarm service

in APL Demo,alarm service is show notification in status bar ..when i
click on status bar, it cannot show expandedText...     how to show
expandedText ????
--~--~---------~--~----~------------~-------~--~----~

2. How to List Contacts

Does somebody knows how to list the contacts based on the given intent
? The Intent API tells of how to invoke the intent with the
VIEW_ACTION content://contacts/.

However, how can I access the contact data model? For example, if I
would like to list just the phone numbers of my contact list how can I
do it?

thanks,
Mario

--~--~---------~--~----~------------~-------~--~----~

3. Proximity Alert Extras

4. Setting the selection color in a ListView

5. Problem connecting to localhost from the emulator

6. Display list in two columns

7. Please update the Notepad examples with "android.provider.BaseColumns._ID" (was: Bad request for field slot 0,-1.)