We really only need two methods here: Connect and Disconnect, and also need a way to retrieve the interface to the billing service. Its job is to connect to the Android billing service and instantiate a IInAppBillingService instance our app can use for interprocess communication. With that out of the way, we need to implement an IServiceConnection for billing. These were ported from the Java sample, and we may not need to use them all. Next, let's define several constants that we will need to use throughout our GooglePlayPurchaseService. Since we have an aidl file that doesn't map to a Java class included in our app, it will get stripped by proguard without adding an exemption.īefore we start anything, go ahead and add permissions for and to your Android application, as they are needed for in-app billing to work. Using proguard is a good idea in general, as it obfuscates and strips unused code from any Java libraries your application is using. You will need to add the following to your Proguard.cfg file: If you are using proguard, which I highly recommend for apps using Java libraries (Google Play Services, etc.). To set them up in your project, download IInAppBillingService.aidl and Bundle.aidl from my sample here,Īnd set the build action to AndroidInterfaceDescription in Visual Studio/Xamarin Studio.ĭoing this will generate several C# classes for interacting with the Android billing service from within your application. You can think of AIDL as Android's version of a contract for interprocess communication. The very first thing you need will be an Android aidl file, along with a custom one needed for Xamarin apps. So for getting started with this, I followed Google's Java sample and ported it to C# (using C# idioms). Implementing In-App Purchases for Google Play NOTE: I would not recommmend installing any of these things without doing your own research An app exists called Freedom, targeted directly at unlocking free in-app purchases on Android.Modify the device's filesystem: at the system, or app level.
The Android APIs are a bit more involved, and Android's openness lends itself to more hacking, in general.įor example, here are the kinds of things Android users can do (a bit more easily than iOS):
Implementing secure in-app purchases for Google Play is a bit trickier than iOS for several reasons. Make sure to take a look at the full source code here if you need the full picture. In this post, I will build on the existing PCL from the iOS sample. If you missed part 1 of this series, read about the basics and how to secure iOS in-app purchases here. Securing Google Play In-App Purchases for Xamarin with Azure Functions
0 kommentar(er)
