You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I publish my app, Google starts auto-test on various devices. Since two releases Google give a NPE with this stack trace:
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.Bundle com.android.vending.billing.IInAppBillingService.getBuyIntent(int, java.lang.String, java.lang.String, java.lang.String, java.lang.String)' on a null object reference
at com.smartmobilesoftware.util.IabHelper.launchPurchaseFlow(IabHelper.java:386)
at com.smartmobilesoftware.util.IabHelper.launchPurchaseFlow(IabHelper.java:338)
at jp.wizcorp.wizpurchase.WizPurchase.buy(WizPurchase.java:416)
at jp.wizcorp.wizpurchase.WizPurchase.access$200(WizPurchase.java:40)
at jp.wizcorp.wizpurchase.WizPurchase$4.run(WizPurchase.java:296)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
In a physical use, no exception...
Google told me that the tested device is Galaxy S6 under Android 5.1. Others 5.1 devices pass all the tests.
The text was updated successfully, but these errors were encountered:
Hello,
Thanks for the logcat file! I tried to trace back your error but I couldn't find why you have this exception as everything seems to be properly initialized.
As I have no way to reproduce it currently, would you be able to make a new build with debug logs activated in IabHelper and attach the resulting logs?
This can be done either by:
Hello,
When I publish my app, Google starts auto-test on various devices. Since two releases Google give a NPE with this stack trace:
In a physical use, no exception...
Google told me that the tested device is Galaxy S6 under Android 5.1. Others 5.1 devices pass all the tests.
The text was updated successfully, but these errors were encountered: