Android Question In-App Billing 3 Library issue with Android v5.0

[Computersmith64]

I have been using the In-App Billing 3 library in myPets for over a year & found when I recently started using Firebase Analytics in the app that the following crash is reported:

http://stackoverflow.com/questions/...mentexception-service-intent-must-be-explicit)

Is there a way to do this in B4A code, or does the library need to be modified?

Thanks - Colin.

 

[Erel]

Which version of the library are you using? It should already be implemented in the latest version.

 

[Computersmith64]

Which version of the library are you using? It should already be implemented in the latest version.

v1.11 - is there a later one?

 

[Erel]

The fix is already there. Can you post the crash report from Firebase?

 

[Computersmith64]

The fix is already there. Can you post the crash report from Firebase?

Here it is - oh & I just noticed that this is from a device running Android v5.0.1:

Exception java.lang.IllegalArgumentException: Service Intent must be explicit: Intent { act=com.android.vending.billing.InAppBillingService.LOCK }
android.app.ContextImpl.validateServiceIntent (ContextImpl.java:1773)
android.app.ContextImpl.bindServiceCommon (ContextImpl.java:1874)
android.app.ContextImpl.bindService (ContextImpl.java:1852)
android.content.ContextWrapper.bindService (ContextWrapper.java:538)
anywheresoftware.b4a.objects.IbHelper.startSetup (IbHelper.java:271)
anywheresoftware.b4a.inappbilling3.BillingManager3.Initialize (BillingManager3.java:44)
com.airlinemates.mypets.starter._service_create (starter.java:321)
java.lang.reflect.Method.invoke (Method.java)
java.lang.reflect.Method.invoke (Method.java:372)
anywheresoftware.b4a.BA.raiseEvent2 (BA.java:179)
anywheresoftware.b4a.BA.raiseEvent (BA.java:163)
com.airlinemates.mypets.starter.onCreate (starter.java:55)
android.app.ActivityThread.handleCreateService (ActivityThread.java:2756)
android.app.ActivityThread.access$1800 (ActivityThread.java:149)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1367)
android.os.Handler.dispatchMessage (Handler.java:102)
android.os.Looper.loop (Looper.java:135)
android.app.ActivityThread.main (ActivityThread.java:5292)
java.lang.reflect.Method.invoke (Method.java)
java.lang.reflect.Method.invoke (Method.java:372)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:908)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:703)

 

[Erel]

The library doesn't create an intent with this name: com.android.vending.billing.InAppBillingService.LOCK
It creates a different one: com.android.vending.billing.InAppBillingService.BIND

It seems like the error is related to the Lucky Patcher hacking tool (google it and you will see). Maybe these errors happen on rooted devices that try to hack the purchase process or this is a hacked version of your app.

 

[Computersmith64]

The library doesn't create an intent with this name: com.android.vending.billing.InAppBillingService.LOCK
It creates a different one: com.android.vending.billing.InAppBillingService.BIND

It seems like the error is related to the Lucky Patcher hacking tool (google it and you will see). Maybe these errors happen on rooted devices that try to hack the purchase process or this is a hacked version of your app.

Oh great! It's hard enough to make a living without scumbags giving users the tools to circumvent advertising & in-app purchases. People are even posting videos on YouTube showing Lucky Patcher users how to steal from some of the most popular apps out there. I'm amazed that Google & the publishers of these apps aren't shutting these thieves down.

- Colin.