Support extending Application singleton about android-inapp-billing-v3 HOT 5 CLOSED

I don't remember this actually :) would you mind to try to change it to just a Context and do a pull request if it will work?

from android-inapp-billing-v3.

Now I see. Activity context is used to initiate purchase flow, no other contexts are valid for this. So maybe you better implement a handler as a singleton and put it under application scope?

from android-inapp-billing-v3.

Yes, the work-around we used was to initialize in the MainActivity and then store a reference in the application singleton. But as Google is moving away from Activity in favor of Fragments, we might have trouble in the future. Anyway, thanks for the good library!

On Sep 9, 2014, at 12:13 PM, "Sergey A. Glukhov" [email protected] wrote:

Now I see. Activity context is used to initiate purchase flow, no other contexts are valid for this. So maybe you better implement a handler as a singleton and put it under application scope?

�
Reply to this email directly or view it on GitHub.

from android-inapp-billing-v3.

But this is not a solution if your MainActivity disposes at some time (by the OS rules), right?
So maybe it is a better solution to change your pattern?

from android-inapp-billing-v3.

Thanks, but our pattern is to use the Application singleton because of this reason.

On Oct 15, 2014, at 10:09 PM, Sergey A. Glukhov [email protected] wrote:

But this is not a solution if your MainActivity disposes at some time (by the OS rules), right?
So maybe it is a better solution to change your pattern?

�
Reply to this email directly or view it on GitHub.

from android-inapp-billing-v3.