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.
Related
We’ve detected that your app is using an old version of the Google Play Billing. By Nov 2021 all the app updates must use version 3 or newer.
How to update this?
Make sure you have updated your Google play billing dependency to com.android.billingclient:billing:3.0.0 or above and implemented any changes that dove happened between the library versions. For more information check out the documentation: https://developer.android.com/google/play/billing/integrate
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
I just got an e-mail from Google saying that they are deprecating the version 6.4.1 of AdMob and I need to upgrade the library in order to use the Ads in the application:
...we are deprecating versions 6.4.1 and lower of the Android Google Mobile Ads SDK on September 15th, 2016.
In order to ensure that your ads continue to serve after September 15th, 2016, please upgrade to Google Mobile Ads SDK 7.0.0 or higher...
The problem is that I have lost the entire project (source code) and certificates, and I want to know the version of my AdMob. This is what I got from reverse-engineering:
public static final int GOOGLE_PLAY_SERVICES_VERSION_CODE = 6587000;
This is the constants value of: android:value="#integer/google_play_services_version"
Is this the version of the Google Play Services or the Admob? What version 6587000 represents (6.5.8)? I cannot find anything on the internet compared to the Google Play Services release notes.
Last version of Admob standalone SDK is 6.4.1. After that all new versions comes with Play Services. I could not find which version it was introduced but as far as I remember It was with Play Services 8.
But android:value="#integer/google_play_services_version" comes with the Play Services 13. So if your app has integer/google_play_services_version then it is using new versions of Admob, so you will not have any problem with the depreciation.
Also consider this old note from Google; "On August 1, 2014, the Play Store will stop accepting new or updated apps that use the standalone Google AdMob SDK. The SDK does not use the Advertising ID, and will therefore be non-compliant with the Google Play Ad Policy on this date."
Version 6.4.1 does not have Advertising ID. So if you updated your app after August 1, 2014, then your app will have newer versions of Admob.
yes , eg play service version 4.1.00 has code 4100000 and version 6.5.87 has code 6587000.but you can not decide the ad sdk version (especially for android). In the mail they mentioned the ad sdk version. you can view some confusing version history for android here and here
if your app is published after August 1, 2014. you are not worry much about this email.
google play service introduce sdk 4.0 onwards release_notes.
note if your app has integer/google_play_services_version then that is not mean you are using new versions of Admob (after 6.4.1 introduce gps module in the ad).
Email from Admob was very confusing to me.
Here is reply I found out on admob developer forum by Admob team. Hope this helps to clarify further
****"Hi Josue,
After talking with the rest of the team, the note you have gotten about the SDK needing to be higher than v6.4.1 refers to a legacy, standalone Mobile Ads SDK that was deprecated back in February 2014, and that had its own versioning system. That deprecation does NOT refer at all to the use of Google Play services. What that means is even if you are using Google Play services 4.0 which was released back in October 2013, you are still OK.
Vu Chau
Mobile Ads SDK Team"****
Last line makes it very clear, if your google_play_services_version > 4 , you don't need to make immediate update however it's good practice to upgrade to latest versions of play services library
Date 9/9/2016 Updated link from Admob for further clarification- https://firebase.google.com/docs/admob/android-legacy-release-notes
I am trying to find change-logs for Google Play Services for Android.When I am trying to use latest Google Play Service SDK with my Library project My app crashes since It was complied with earlier version of Google Play Service SDK.New SDK doesn't contains certain methods which were available in previous versions.
I would really appreciate If somebody can point me out to Google Play services changelog.
Thanks.
There you go,
GOOGLE PLAY SERVICES RELEASE NOTES:
https://developers.google.com/android/guides/releases
It helped me a lot.
Here is Google's blog post explaining the changes in Google Play Services 4.1 (aka Rev. 14), released in early January 2014:
http://android-developers.blogspot.com/2014/01/google-play-services-41.html
Try this,
Go to your project
Right click and select Android Tools
Select option Add Supportive Library
Done.