Configuration is null about androidbillinglibrary HOT 5 CLOSED

I suggest putting a break-point in BillingController.setConfiguration and make sure it's called by AbstractBillingActivity.onCreate.

from androidbillinglibrary.

It's actually what I did, i changed the code as below:

 /**
 * Sets the configuration instance of the controller.
 * 
 * @param config
 *            configuration instance.
 */
public static void setConfiguration(IConfiguration config) {
    if(config == null)
        Log.w(TAG,"setConfiguration param is null");
    configuration = config;
    if(configuration == null)
        Log.w(TAG,"setConfiguration is not working");       
}

I got the two logs warning. That's why i got lost, how "this" (InAppBilling extends AbstractBillingActivity) could be null if actually it's "this" who called the method....

So my guess is something happened after the call which change the configuration to null...

Thanks for your support

from androidbillinglibrary.

You should get the two log warnings when setConfiguration is called by onDestroy (which sets it to null).

I suggest to add a break-point and debug. Make sure setConfiguration is called on onCreate before onDestroy is called.

from androidbillinglibrary.

Thank you I fixed it. Actually I called onBackPressed() too quickly so the onDestroy was called before onPurchase{State}()

Now I wait for the answer. But it rises a new problem, what if there is no answer? I mean it could happen that phone lost the network or any other problem. In this case I don't want the user stock on my purchase screen. How can i handle this case please?

Is there any "default" method which will be call after a timeout?

Many thks.

from androidbillinglibrary.

Unfortunately that's an Android in-app billing issue. There's not much our library can do about it.

from androidbillinglibrary.