Something doesn't sound right about relying on notifications for
anything.

No way that notifications can be made reliable at least not in any
guaranteed time where "any time" may be infinite.  What happens if the
user shuts off his internet right after purchasing, for example?



On May 23, 4:17 pm, keianhzo <[email protected]> wrote:
> Ok, thank you.
>
> I have replied in the issue 14 list with my problem details.
>
> On May 19, 12:14 pm, Kostya Vasilyev <[email protected]> wrote:
>
>
>
> > 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. Thebilling
> > > system is failing in such a basic thing as sending notifications.
> > > Maybe I should place an issue in the marketbilling issues list.
>
> > > On May 16, 1:19 pm, keianhzo<[email protected]>  wrote:
> > >> 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
> > >>billingissues, 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- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to