NullPointerException from Billing API.

[GoogleCodeExporter]

Below error very frequently occursin API v1~v2 both.
And the exactly same apk package which generate below erro
WORKS on other devices WITHOUT any errors.
What happends? whey keep market billing module make 
below critical error?

We developer don't care 
whether the issue belong Google Play apk or framework or Billing API team.
Fix it. do not keep silent or mambo jumbo.
This is obiusly your problem.

--------------------------------------------------------
java.lang.RuntimeException: Unable to start service 
com.zzzzzzzzzzzz.yyyyyyyyyyy.BillingService@41b15648 with Intent { 
act=com.android.vending.billing.RESPONSE_CODE (or status_change_code) 
cmp=com.zzzzzzzzzzzz.yyyyyyyyyyy/com.zzzzzzzzzzzz.yyyyyyyyyyy.BillingService 
(has extras) }: java.lang.NullPointerException
 at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2388)
 at android.app.ActivityThread.access$1900(ActivityThread.java:127)
 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1214)
 at android.os.Handler.dispatchMessage(Handler.java:99)
 at android.os.Looper.loop(Looper.java:137)
 at android.app.ActivityThread.main(ActivityThread.java:4499)
 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:794)
 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:561)
 at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
 at com.zzzzzzzzzzzz.yyyyyyyyyyy.BillingService.onStartCommand(Unknown Source)
 at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2371)

Original issue reported on code.google.com by newandro...@gmail.com on 21 Nov 2012 at 5:13

[GoogleCodeExporter]

You should test for nul intent.
http://stackoverflow.com/questions/6759802/android-inapp-purchase-null-pointer-e
xception/12488357

And yes, maintenance of in-app-billing code leaves a lot to be desired. It's 
almost as if Google simply has zero focus on in-app-billing services.

Original comment by b.st...@gmail.com on 24 Nov 2012 at 10:10

[GoogleCodeExporter]

NO, you wronly pointed out.
And the code snippet 'if(intent == null)' part always in the onStartCommand.
I'm very highly experienced professional in this industry.

Above error occure
eefore reaching the onStartCommannd Callback. 
The workflow never touched the onStartCommannd part even 'if(intent == null)' 
part.

That is why the solution never exist
and also no one got the solution.

THIS IS BILLING MODULE ERROR
OR
FRMAMEWORK ERROR. 
which is very frequently occure.

YOU MUST DIG INTO THE PROBLEM.

(P.S : why you google people just let some ciritical eror stay in the platform?
not only this error.
You people must seriously taking this report and other billing relatied issue
which keep grinding Google technology reputation.)

Original comment by newandro...@gmail.com on 25 Nov 2012 at 10:58