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. CSS support on WebView

Hello All,

I have a requirement of using a WebView to display the jsp pages from
the server which uses JSTL. Here we have buttons in tabular form
displayed using <table> tag and the first button needs to shown as
selected with the CSS enabled for that selection. The buttons here are
simple input type button with in an anchor tag to navigate to other
pages

<a onmouseover="focusOnMouseOutOnHover(${status.index})"
onmouseout="focusOnMouseOut('abc_0','btn');" id="abc_${status.index}"
class="btn" href="abcd.jsp?cid=${abc.id}"><input type="button"
name="abButton_${status.index}" value="${name}" title="$
{fn:escapeXml(abc.name)}" class="flex-btn"></a>

but the problem is that on device the default focus is not always on
the first button and after that the trackball scrolling is also not
definite. It sometimes scrolls properly and sometimes does not scroll
at all through all the elements in the page. We need the focus on the
first button always when ever we navigate to the page either first
time or through the back key. At present we are calling a javascript
function on onLoad of the <body> to set the focus on the first button
and then update the CSS class also to show it as focussed and
selected.

We have lots of CSS applied on the page to get the rich look of the
Android client on these pages.

Please let me know if there is some solution for this. Is it the
problem of CSS being applied or WebView is not able to support the CSS?

-- 

2. Tampilan 3d home untuk android

http://goo.gl/wKx0

 

 

cool

-- 
"Indonesian Android Community [id-android]" 

3. ROM Eclair Magic

4. Example that prints 1 2 3 4 on A A A A?

5. programatically press a button

6. Popping up a custom Dialog from a Widget (AppWidget)

7. system hangs while giving Android build