java.lang.RuntimeException

Failure delivering result ResultInfo{who=null, request=10001, result=-1, data=Intent { (has extras) }} to activity {com.eknathkadam.grammaruplite/com.webrich.base.ui.GoogleInAppPurchaseActivity}: java.lang.NullPointerException

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via Stack Overflow by Mac
    ,
  • Stack trace

    • java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=10001, result=-1, data=Intent { (has extras) }} to activity {com.eknathkadam.grammaruplite/com.webrich.base.ui.GoogleInAppPurchaseActivity}: java.lang.NullPointerException at android.app.ActivityThread.deliverResults(ActivityThread.java:3141) at android.app.ActivityThread.handleSendResult(ActivityThread.java:3184) at android.app.ActivityThread.access$1100(ActivityThread.java:130) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1243) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:4745) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.NullPointerException at com.google.billing.Base64.decode(Base64.java:434) at com.google.billing.Security.generatePublicKey(Security.java:87) at com.google.billing.Security.verifyPurchase(Security.java:66) at com.google.billing.IabHelper.handleActivityResult(IabHelper.java:437) at com.webrich.base.ui.GoogleInAppPurchaseActivity.onActivityResult(GoogleInAppPurchaseActivity.java:238) at android.app.Activity.dispatchActivityResult(Activity.java:5192) at android.app.ActivityThread.deliverResults(ActivityThread.java:3137) ... 11 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.