Open GoogleCodeExporter opened 8 years ago
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
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
Original issue reported on code.google.com by
newandro...@gmail.com
on 21 Nov 2012 at 5:13