In our android app, we are using in app billing using IabHelper wrapper library. Example
https://github.com/googlesamples/android-play-billing/tree/master/TrivialDrive
Now, Google added newer version of the library with lot of changes to it.
https://developer.android.com/google/play/billing/billing_library.html
Which version should we use? When will the Olderversion(v3) of the biller library expire?
As said on google official documentation, the AIDL way is/will not be supported anymore,
https://developer.android.com/google/play/billing/migrate
This topic describes how to migrate away from a billing integration
that uses the Android Interface Definition Language (AIDL). Accessing
Google Play's billing system using AIDL is deprecated, and all
integrations must use the Google Play Billing Library in the future.
This link also includes a guid to migrate from AIDL to the new billing library.
Related
I am developing kotlin project, when i upload release bundle in google console, following warning arised. How to fix this warning?
1 MESSAGE FOR VERSION CODE 49
Warning
The developer of play-services-safetynet (com.google.android.gms:play-services-safetynet) added the following note to SDK version 17.0.1:
The SafetyNet Attestation API is being discontinued and replaced by the new Play Integrity API. Begin migration as soon as possible to avoid user disruption. The Play Integrity API includes all the integrity signals that SafetyNet Attestation offers and more, like Google Play licensing and better error messaging. Learn more and start migrating at https://developer.android.com/training/safetynet/deprecation-timeline
Learn more about the SDKs that you're using and make informed SDK choices with Google Play SDK Index.
As warning says some part of Android API used by your project is deprecated, you are softly pushed to migrate to the new API.
To fix this issue you have to do this migration. Docs you have shared contains migration guide.
I'm new to Unity IAP. When looking for a way to integrate Google Play IAP into a unity project, I found the "Use the Google Play Billing Library with Unity" documentation which states:
The Google Play Billing Unity plugin will not be receiving updates moving forward. This means that the plugin will remain specific to Google Play Billing Library 3. Additionally, any apps that are updated after November 1, 2022 will no longer be able to use the plugin.
Does Google provide an alternative? Or should I just use Unity's IAP integration directly instead?
I came across the same text just now. I believe you are correct in your assumption that Unity IAP is the correct replacement for this, since according to their documentation UnityIAPGooglePlay the current version of this plugin already uses Google Play Billing v4, which is the minimum required version starting Nov 1.
Google provides a new way to implement in-app update : https://developer.android.com/guide/app-bundle/in-app-updates that can be used to force users to update their app with the latest version available.
To be able to use this new feature, it requires the use of Play Core Library 1.5.0 or higher : https://developer.android.com/guide/app-bundle/playcore
It is possible to use it from Xamarin and to implement in-app update with this new capability ?
Regards
UPDATE: CHECK https://github.com/PatGet/XamarinPlayCoreUpdater
I was able to come up with the Xamarin binding for the play core library which can be found on my drive here
Will be packaging it to NuGet soon, will update here once I do
Why are there two versions of TrivialDrive?
https://github.com/googlesamples/android-play-billing
Which version should be the main reference project for learning in-app billing? What's the difference between the versions?
A little searching shows that Trival Drive V2 sample has a shared build.gradle file:
https://github.com/googlesamples/android-play-billing/blob/master/TrivialDrive_v2/shared-module/build.gradle
which has the following line:
compile 'com.android.billingclient:billing:dp-1'
Looking at the documentation here:
https://developer.android.com/google/play/billing/billing_library.html
Shows that Google just released a new version of the Billing Library release dp-1:
Starting with Play Billing Library release dp-1 (June 2017), the minimum
supported API level is Android 2.2 (API level 8). The minimum supported
In-app Billing API is version 3.
And specifically calls out changes to the minimum support Android API and In-app Billing API.
Given the Trivial Drive V2 sample app(s) has a Wear 2.0 example - this version has billing support on Wear 2.0 apps.
TrivialDrive_v2 demonstrates a new way of integration with Google Play Billing.
It's based on the latest release of Play Billing library (currently 1.0) and tries to promote the best practices of integration with it.
TrivialDrive sample was kept for those that still use an integration via AIDL file (e.g. C++ developers).
Trivial Drive V2 is refreshed sample for new release of Google Play Billing Library. See that link: https://android-developers.googleblog.com/2017/06/money-made-easily-with-new-google-play.html
According to Android developer documentation, Google Play Services library provides an interface to the hosting application so that, at runtime, it can access to Google Play services APK through interprocess communication.
Considering the following configuration where an android application includes Google Play Services library and a SDK that also includes Google Play Services library, as shown below:
MyApplication
Google Play service v.XX
MySDK
Google Play Services v.YY
Since the SDK and the hosting application include different versions of Google Play Services library, is version YY fetched at MyApplication build time instead of version XX ? Is the final application built with the two different versions (XX and YY) and in this case which one is called at runtime?
Best Regards,
You can use command ./gradlew app:dependencies at Android Studio console to see all dependencies and which version is being used.