Service Intent must be explicit about play-billing-samples HOT 7 CLOSED

Anyone?

from play-billing-samples.

Are you using new Play Billing library or modified TrivialDrive sample?
From what I see, they both explicitly define the package inside serviceIntent:
serviceIntent.setPackage("com.android.vending");
Maybe, it's just a side-effect of "cracking" the system? How often does it happen?

from play-billing-samples.

I am using the new library. Well, the number of crashes is low but it also happens on startup when checking purchases and it's not good that the app crashes even though the user has installed illegal software on his device. You should look into this

from play-billing-samples.

My guess is that hack tools sometimes are removing explicit package name from the intent on the fly and trying to represent themselves as a Play Store.
So there is not much we can do except including other explicit variables inside the intent in next library release, but they can also be removed.
I think the best solution for developers would be catch IllegalArgumentException from BillingClient.startConnection method.
And for security we strongly recommend using our backend API for all purchases verification.

from play-billing-samples.

FYI, while I understand why it's recommended to use the backend API for purchase verification, this only really works if the app has user sign-in and a backend.

from play-billing-samples.

@gorgon of course I am using backend verification with PHP code. I just wanted to know if there was a gentle way to solve the crash without having to catch the Exception explicitly on my side.

from play-billing-samples.

Thanks for reporting this.
I'm closing this issue because this forum is for issues with the sample.

Stackoverflow might be a better forum.

Please reopen if you still think this is an issue with the sample.

from play-billing-samples.