[AC-3124] Issue with Android In-App Billing Module
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2012-03-26T12:12:24.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Appcelerator Modules |
Labels | android, module |
Reporter | Frank Apap |
Assignee | Mauro Parra-Miranda |
Created | 2012-03-05T06:03:43.000+0000 |
Updated | 2016-03-08T07:48:11.000+0000 |
Description
In my apps android dev console I see the following crash reports (note: I haven't been able to recreate). A similar issue in a different part of the code was found and fixed recently.
java.lang.RuntimeException: Unable to start service ti.inappbilling.BillingService@405e8d38 with Intent { act=com.android.vending.billing.RESPONSE_CODE cmp=com.apsquared.tvfoodmaps/ti.inappbilling.BillingService (has extras) }: java.lang.NullPointerException
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2150)
at android.app.ActivityThread.access$2800(ActivityThread.java:124)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1043)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3906)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:840)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:598)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at ti.inappbilling.BillingService.handleCommand(BillingService.java:289)
at ti.inappbilling.BillingService.onStart(BillingService.java:73)
at android.app.Service.onStartCommand(Service.java:428)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2137)
... 10 more
I know you're not able to reproduce, but could you include a complete log for context?
What do you mean by complete log - that is basically all the information I get from the crash report.
Context of what is happening in the app - do you not get any more log information from the crash report, only the exception stack trace?
Yea, that is all I get. This was very similar to the last (similar issue, TC-626).
Closing since it's a dup.