Google Play Billing v 6.2.1 with SDK 34 #3477
Replies: 20 comments 57 replies
-
|
Please ensure you have updated the extension as well as the manifest additions. Updating only one can cause issues. |
Beta Was this translation helpful? Give feedback.
-
|
@stephanberger4 That ANE also mentions the minSdkVersion has to be 24 now instead of 19, not sure if that would affect it as well? There's also the new ProxyBillingActivityV2, the migration doc lists all of the new changes here: |
Beta Was this translation helpful? Give feedback.
-
|
The SDK updates according to the distriqt's instruction worked well. Make sure also to update also service ANE's |
Beta Was this translation helpful? Give feedback.
-
|
Hello stephanberger4 - did you find a solution to this? I've downloaded the latest ANEs (maybe not all of them) but receiving the following error message when uploading my APK: Your app currently uses Play Billing Library version AIDL and must update to at least version 6.0.1 to make use of the latest monetization features on Google Play. |
Beta Was this translation helpful? Give feedback.
-
|
Hi
Yes, I had to buy the ANE on this website to fix the error : https://airnativeextensions.com/extension/com.distriqt.InAppBilling/
Envoyé à partir de Outlook pour Android<https://aka.ms/AAb9ysg>
…________________________________
From: jason68000 ***@***.***>
Sent: Saturday, March 29, 2025 3:40:38 AM
To: airsdk/Adobe-Runtime-Support ***@***.***>
Cc: stephanberger4 ***@***.***>; Mention ***@***.***>
Subject: Re: [airsdk/Adobe-Runtime-Support] Google Play Billing v 6.2.1 with SDK 34 (Discussion #3477)
Hello stephanberger4 - did you find a solution to this? I've downloaded the latest ANEs (maybe not all of them) but receiving the following error message when uploading my APK:
Your app currently uses Play Billing Library version AIDL and must update to at least version 6.0.1 to make use of the latest monetization features on Google Play.
—
Reply to this email directly, view it on GitHub<#3477 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABQWF7RCXJGIBIWGDW5G7PT2WV3QNAVCNFSM6AAAAABOOQHED2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRVGU2TENI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello! Yes, I purchased the same extension for In-App purchases. I've managed to get the most part working but still having a few setup issues. It looks though like your a few steps ahead of me in getting everything working. Would it be okay if I sent you a private message and you could give me a few tips of your development of this? I can post my email here if that would be okay! Many thanks! Jason |
Beta Was this translation helpful? Give feedback.
-
|
Hello again! I've just posted out two discussions in relation to my last reply above. I'm not sure where the Google Play Billing lives so I could possibly update it manually. I'm receiving an error saying I need to use at least version "6.0.1" so I would love to use version 6.2.1 as mentioned originally in this post. I also had another question above Alternative Billing API. Sorry if this seems a double up, I'm not sure of the exact protocol in posting out here, I know people mention not to ask another question within a previous one! Jason |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Here's my manifest. Try to check if you have the same thing in your xml :
<manifestAdditions><![CDATA[
<manifest android:installLocation="auto">
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="34"/>
<!-- Permissions -->
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="com.android.vending.BILLING" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
<uses-permission android:name="android.permission.WAKE_LOCK"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
<!-- Google Play Billing query -->
<queries>
<intent>
<action android:name="com.android.vending.billing.InAppBillingService.BIND" />
</intent>
</queries>
<application>
<!-- Distriqt In-App Billing Activity -->
<activity
android:name="com.distriqt.extension.inappbilling.activities.ProductViewActivity"
android:exported="false"
***@***.***:style/Theme.Translucent.NoTitleBar" />
<!-- Google Play Billing setup -->
<meta-data android:name="com.google.android.play.billingclient.version" android:value="6.2.1" />
<!-- Billing activities -->
<activity
android:name="com.android.billingclient.api.ProxyBillingActivity"
android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation"
android:exported="false"
***@***.***:style/Theme.Translucent.NoTitleBar" />
<activity
android:name="com.android.billingclient.api.ProxyBillingActivityV2"
android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation"
android:exported="false"
***@***.***:style/Theme.Translucent.NoTitleBar" />
</application>
</manifest>
]]></manifestAdditions>
…________________________________
De : jason68000 ***@***.***>
Envoyé : lundi 31 mars 2025 00:58
À : airsdk/Adobe-Runtime-Support ***@***.***>
Cc : stephanberger4 ***@***.***>; Mention ***@***.***>
Objet : Re: [airsdk/Adobe-Runtime-Support] Google Play Billing v 6.2.1 with SDK 34 (Discussion #3477)
Hello again!
I've just posted out two discussions in relation to my last reply above. I'm not sure where the Google Play Billing lives so I could possibly update it manually. I'm receiving an error saying I need to use at least version "6.0.1" so I would love to use version 6.2.1 as mentioned originally in this post. I also had another question above Alternative Billing API. Sorry if this seems a double up, I'm not sure of the exact protocol in posting out here, I know people mention not to ask another question within a previous one!
#3732<#3732>
#3733<#3733>
Jason
—
Reply to this email directly, view it on GitHub<#3477 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABQWF7U4NA6BG3VIMPO74IL2W72BJAVCNFSM6AAAAABOOQHED2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRWG43DIMA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I suggest you update to the latest release. A lot of these additions are handled via the newer build process now and aren't needed. https://docs.airnativeextensions.com/docs/inappbilling/migration-v16.0 |
Beta Was this translation helpful? Give feedback.
-
|
Hey stephanberger4 - I tried using your manifest but not much luck. I didn't see which ANEs you were using as I'm now I getting weird Build errors. Are you able to tell me which ANEs you are using. Could you upload them somewhere or give me the github locations! Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
(Please note it's against the license agreement to redistribute the distriqt extensions so please don't upload them anywhere). |
Beta Was this translation helpful? Give feedback.
-
|
My bad! :-/ |
Beta Was this translation helpful? Give feedback.
-
|
Maybe I can be of some help with Application.xml Here I'll share my application.xml files for these two. Purchases are working well for me with Distriqt extension |
Beta Was this translation helpful? Give feedback.
-
|
Hey GeneralVimes!
Thanks very much for the xmls files! Here's where I've been and where I'm at now:
As I mentioned in a previous message when I would upload my APK (I added <uses-permission android:name="com.android.vending.BILLING" />) I would receive the following error message:
Your app currently uses Play Billing Library version AIDL and must update to at least version 6.0.1 to make use of the latest monetization features on Google Play.
I managed to get APM working well and it downloaded all the necessary ANEs and updated my manifest (which is very similar to yours btw). I was able to build my APK and get past the above error message. My app was approved but when I try to setup and configure In-App through the Google Play Store, I see this message:
To add in-app products, you need to add the BILLING permission to your APK
So I'm not sure I'm doing this whole thing correctly or not. From what I read with the documentation I need to setup In-App billing products and then reference them in my app - which I assume I need to upload and APK which allows In-App billing.
Have you been through these errors/quirks before? I feel like I'm going around in circles with this one. Am I correct though in assuming I need to be referencing code in my APK (which I believe I'm doing now) before I can configure In-App products in the Google Play Console.
Thanks!Jason
On Friday, April 4, 2025 at 09:54:19 AM GMT-6, GeneralVimes ***@***.***> wrote:
Maybe I can be of some help with Application.xml
On my repository I created branches for the "clean" game and for the game with SDKs.
Here I'll share my application.xml files for these two.
Purchases are working well for me with Distriqt extension
xmls.zip
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That BILLING permission should be automatically added to your manifest now with the newest InAppBilling ANE (v16+) when packaging -- I'm just updating some apps myself moving from v15 to v16, and saw that it was added by the new gradle dependency process (I checked it in APK Analyzer in Android Studio to see what it had added to AndroidManifest - might be worth checking that too). Are you using a new-ish AIR SDK version when packaging? I'm not sure if there's a specific AIR version needed to support how the newest ANEs work, though it seems to work for me with 51.1.x Also make sure you're not still using BuildLegacyAPK in your application descriptor anymore (and package as AAB if this is a newer app, since Google doesn't allow APKs except for updating old apps). I'm not sure if anything has changed recently, but the process I've used in the past for adding IAPs was to first upload an APK/AAB to a test/alpha track in the Play Console (so there was something there that had the BILLING permission), then it would let me add the individual IAPs through the Play Console. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks FliplineStudios! Perfect,! I've just uploaded my APKs to a test track! I've just noticed when I click the button next to the message "To add in-app products, you need to add the BILLING permission to your APK" it now re-directs to the testing section I just uploaded to. It didn't do this before, I think it just went to a Help page. |
Beta Was this translation helpful? Give feedback.
-
|
Have you checked to make sure the BILLING permission is included in the APK you uploaded? In the Play Console under "Test and release" > "App bundle explorer", you can click on an uploaded APK/AAB and check the "Permissions" section to make sure it's included there (mine show "android.permission.INTERNET, com.android.vending.BILLING") |
Beta Was this translation helpful? Give feedback.
-
|
Hey FliplineStudios - Yes, looks like you're correct. When I check the permissions for my APK it only shows the following: android.permission.READ_EXTERNAL_STORAGE So I must be missing one very important part of the setup puzzle as I see no android.permission.INTERNET or com.android.vending.BILLING - as not many others explicitly include these in their manifest. When I run some test code I can display the following: InAppBilling.service.version = 16.1.2 BIG QUESTION: As I don't explicitly include com.android.vending.BILLING and android.permission.INTERNET and they are not listed in my permissions what I missing in my Build / Setup ? When I include com.android.vending.BILLING and android.permission.INTERNET and then upload my APK I receive the error: Your app currently uses Play Billing Library version AIDL and must update to at least version 6.0.1 to make use of the latest monetization features on Google Play. My project uses the following ANEs and application descriptor generated (which is very similar to other posts above) com.distriqt.Core.ane (2905 KB) When I remove these ANEs from the project I receive dozens of errors, so the code it being used, to a certain extent. I'm calling this code as quick start: var service:BillingService = new BillingService().setGooglePlayPublicKey( GOOGLE_PLAY_INAPP_BILLING_KEY ); I'm not much of a Java guy so when I hear "new gradle dependency" how can I verify it's being used, or investigate it further? I think I am missing something very fundamental and important. Do I need to call/init something to kick off access to Google's Billing Libraries? Jason |
Beta Was this translation helpful? Give feedback.
-
|
This sounds like what would happen if you are using the legacy build method. This will happen if you haven't supplied a version of the android SDK in your adt.cfg or via the air SDK manager (or if you are using < AIR 50.2). Can you enable debug outputs (via adt.cfg or the air SDK manager) and post the output in ~/adt.log. This should tell us what's being used. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using Flashbuilder 4.7. Latest SDK, latest Java. I'm just trying to figure out how to output the adt.log. I've seen other people post this so I'm just trying to figure it out. I've tried adding the entry in adt.cfg but I can't generate the adt.log file. I'll keep poking around. If you know how to configure FlashBuilder 4.7 to handle what you mentioned above let know know and i'll try it. If it helps I can also create a dummy project in FB 4.7 and I could show you that. Or if anyone else is using FB 4.7 they could give me some tips! |
Beta Was this translation helpful? Give feedback.
-
|
In the AIR SDK's lib folder, there should be an adt.cfg file already (it just has everything commented out with a # before each setting so everything is disabled). You would just remove the # before Make sure you're editing adt.cfg for the specific AIR SDK you're using to package and not whatever Flash Builder uses as a default SDK, in case that's something different. You can also put an adt.cfg file in the ".airsdk" folder with just (I've just tried that myself, and I can see the multiple lines of "Adding gradle dependency" for the ANEs I'm using) |
Beta Was this translation helpful? Give feedback.
-
|
Here's my ADT.log: APK Packager entry point I have Android Studio installed. Here's a snippet from my ADT.cfg file: DebugOut=true I'm not sure how to add the version of the android SDK here. Also I read I need to use forward slashes for the path. If anyone has their ADT.cfg that works, that would be great! I could try that with my Build. Also, I don't see any references to "gradle". Jason |
Beta Was this translation helpful? Give feedback.
-
|
That looks odd, my log looks very different from that... this reminds me of the legacy output I'd see back before the Android platformsdk was used. You're not using |
Beta Was this translation helpful? Give feedback.
-
|
This is definitely the legacy build output and will be the cause of your problems. Firstly check you have installed android studio, then open the SDK manager in android studio and check where the SDK install path is. (While you are there check you have v34.0.0 of the build tools installed) Next install the AIR SDK manager (https://airsdk.dev). This tool is the easiest way to configure AIR. Go to the configuration page and enter the path to your android SDK. Once you've done that, check the log again after a build and it should look significantly different. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using FB 4.7 and the output I posted when I exported my APK. I've specified the Android SDK directory in adt.cfg (forward slashes needed?) but I'm not sure it's even being called as when I put in a bad value or take it out the output log is exactly the same! So yes, I'm guessing I'm still using the legacy build
Michael mentioned this would happen if I don't specify a version of the android SDK in your adt.cfg. I'm not sure of the syntax of doing this, nor what else I need in adt.cfg to get Android SDK used in the build process.
If someone had their adt.cfg file for all this I would definitely try that - and also what downloads are needed for Android Studio to work with the build!
I'm still searching for information on how Android SDK/Studio works in all of this, and how to Debug when things aren't working correctly!
On Saturday, April 5, 2025 at 10:48:25 AM CDT, FliplineStudios ***@***.***> wrote:
That looks odd, my log looks very different from that... this reminds me of the legacy output I'd see back before the Android platformsdk was used. You're not using <BuildLegacyAPK> in your application descriptor XML, correct? And within Android Studio, you have the Build Tools downloaded for the version you're trying to package (I'm guessing 34.0.0 or newer since that's what Google requires now)?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I've always just added it at the end of my For having the correct Build Tools in Android Studio, here's what I do:
After that is installed, you should see a folder in your Android SDK folder build-tools for any versions you've installed (for example, in your case in C:\Users\Jason\AppData\Local\Android\Sdk\build-tools you should see a 34.0.0 folder, or whichever you installed). You could also take a look at that folder now to make sure there's some version of build-tools installed, and if not (or if it's lower than your targetSdkVersion) you can go through the steps above to install it. |
Beta Was this translation helpful? Give feedback.
-
|
I've tried all the suggestions but unfortunately I'm still on the Legacy Build. I have a few suggestions to try and if anyone wanted to help me with their working development environment - that would be amazing! Idea #1: Would anyone be willing to generate and upload their adt.log file. I would like to compare this with mine and see where they are similar and at what point them diverge into the non-Legacy Build. Idea #2: Break your non-Legacy Build at different points, and post the errors etc. If someone has a working non-Legacy Build, would they be willing to try break their build at different points so they can share with me the errors and how they fail. For example, if you rename your android SDK directory to something else and see where your build fails. I've done this at different points and I nothing happens. I can't see any change or any errors when generating an APK. Idea #3: How can I trace through the point where execution hits the Android SDK? Or if anyone has any better ideas for anything I could try! :-) |
Beta Was this translation helpful? Give feedback.
-
|
@jason68000 For reference, here's what my adt.log looks like when it's building correctly for an AAB (with older ANEs): And here's another when it's building correctly for an APK (with the newer ANEs, so you can see all the lines about gradle dependencies): Very different from the legacy packaging like you were seeing. I can see something similar to your output (with the older AAPT method) if I use an older AIR SDK, or if I have I'm calling adt directly for packaging from the command line, not sure if Flash Builder does something different in how it starts the packaging process. I've also got JAVA_HOME pointing to the Android Studio jbr folder since it needs Java 17 for packaging now, not sure if that makes a difference if you're using a different version? |
Beta Was this translation helpful? Give feedback.
-
|
One more suggestion: If anyone know the internal workings of this non-Legacy Build, they could help me trace execution through. In other works, really look at what happens in the background, what programs call what programs and load what configs files etc... At some point for example execution hits the Android SDK, where mine obviously doesn't. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, thanks FliplineStudios! That's some great information to work on. Would it possible to have a look at your command line in calling adt directly. There could be something there I'm missing! I'm just about to crash in for the night but I'll go through everything in the morning! Jason
On Saturday, April 5, 2025 at 09:59:47 PM CDT, FliplineStudios ***@***.***> wrote:
@jason68000 For reference, here's what my adt.log looks like when it's building correctly for an AAB (with older ANEs):
adt_log_aab.txt
And here's another when it's building correctly for an APK (with the newer ANEs, so you can see all the lines about gradle dependencies):
adt_log_apk_newanes.txt
Very different from the legacy packaging like you were seeing. I can see something similar to your output (with the older AAPT method) if I use an older AIR SDK, or if I have <BuildLegacyAPK>true</BuildLegacyAPK> in my application XML, but otherwise I'm always seeing it go through the new packaging. If I try to give it a bad path for the Android SDK (using -platformsdk), it actually outputs an error (UsageError: Could not locate adb) and doesn't try to package anything after that.
I'm calling adt directly for packaging from the command line, not sure if Flash Builder does something different in how it starts the packaging process. I've also got JAVA_HOME pointing to the Android Studio jbr folder since it needs Java 17 for packaging now, not sure if that makes a difference if you're using a different version?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
He again FlipLineStudios, I just saw another post where a developer was having trouble building through FB 4.7, but at least he was off the legacy build. So maybe I can use FB 4.7, but I'm still wouldn't mind have alternative build methods and development tools in case I run into similar problems in the future! :-) |
Beta Was this translation helpful? Give feedback.
-
|
I develop with FlashDevelop, but I mainly just use that to generate the SWF, and then I always package on the command line using the latest stable AIR SDK / adt version afterwards using that SWF. So basically the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the options! I'll look at them over the next few days. I might focus now on your manual package creation rather than figuring out why FB 4.7 can't get by Legacy Build. I've created a separate discussion as I think this one has gone on long enough! :-) If I could possibly pick your brains in regards to this FliplineStudios I should be good once I have the basics down. Let me try and few things and then I'll post out any questions to: |
Beta Was this translation helpful? Give feedback.
-
|
@jason68000 Ah there's your issue, I missed that you were using FlashBuilder previously. FlashBuilder calls directly into the AIR sdk build process and bypasses a lot of the newer AIR features. As far as I'm aware it doesn't support the new build process as it directly calls the legacy process. Honestly FlashBuilder was a great IDE but it's time to move on. IntelliJ or VS Code are the current solutions we suggest to developers. |
Beta Was this translation helpful? Give feedback.
-
|
Hey FlipLineStudios! I've posted a few question in relation to your method. Or if you had a zip file with how you do this I could work through it: #3740 |
Beta Was this translation helpful? Give feedback.
-
|
I'm also looking at alternative development environments to replace FB 4.7. I'm trying to get VSCode working with MXML and receiving a simple error saying ActionScript class cannot be found. I've started another discussion (so we can put this discussion to bed): |
Beta Was this translation helpful? Give feedback.
-
|
Hello again everyone! I need to move to Version 7.0.0 of Play Billing (and everyone else I guess!) but I can't find my in the way of documentation. I've created a discussion in regards to this, if anyone wanted to help out: Jason |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, wrong discussion. Here's the correct one: |
Beta Was this translation helpful? Give feedback.
-
|
v7 is in development. |
Beta Was this translation helpful? Give feedback.
-
|
One last question for all the developers in this discussion. Anyone developed/released cross-platform for Apple/Google? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, just checking : did you already release the v7 version of Billing or not yet ? Thx again ! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, yes v17.1.0 was released with the play billing update required for android 35 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much ! It seems that things have been changed with this new version. My AS3 code was :
InAppBilling.service.addEventListener( InAppBillingEvent.SETUP_SUCCESS, setupSuccessHandler );
InAppBilling.service.addEventListener( InAppBillingEvent.SETUP_FAILURE, setupFailureHandler );
InAppBilling.service.addEventListener( InAppBillingEvent.PRODUCTS_LOADED, productsLoadedHandler );
InAppBilling.service.addEventListener( InAppBillingEvent.PRODUCTS_FAILED, productsFailedHandler );
InAppBilling.service.addEventListener( InAppBillingEvent.INVALID_PRODUCT, productInvalidHandler );
With a function dispose() with : function dispose():void{
InAppBilling.service.removeEventListener( InAppBillingEvent.SETUP_SUCCESS, setupSuccessHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.SETUP_FAILURE, setupFailureHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.PRODUCTS_LOADED, productsLoadedHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.PRODUCTS_FAILED, productsFailedHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.INVALID_PRODUCT, productInvalidHandler );
InAppBilling.service.removeEventListener( PurchaseEvent.PURCHASES_UPDATED, purchasesUpdatedHandler );
InAppBilling.service.removeEventListener( PurchaseEvent.PURCHASE_FAILED, purchaseFailedHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.FINISH_SUCCESS, finishPurchaseSuccessHandler );
InAppBilling.service.removeEventListener( InAppBillingEvent.FINISH_FAILED, finishPurchaseFailedHandler );
InAppBilling.service.removeEventListener( PurchaseEvent.GET_PURCHASES_COMPLETE, getPurchasesCompleteHandler );
InAppBilling.service.removeEventListener( PurchaseEvent.GET_PURCHASES_FAILED, getPurchasesFailedHandler );
}
but ANIMATE throw these messages :
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 71, column 60
Warning: 3606: Use of 'PRODUCTS_LOADED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.PRODUCTS_LOADED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 72, column 60
Warning: 3606: Use of 'PRODUCTS_FAILED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.PRODUCTS_FAILED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 73, column 60
Warning: 3606: Use of 'INVALID_PRODUCT' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.INVALID_PRODUCT'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 102, column 60
Warning: 3606: Use of 'FINISH_SUCCESS' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.FINISH_SUCCESS'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 103, column 60
Warning: 3606: Use of 'FINISH_FAILED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.FINISH_FAILED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 251, column 60
Warning: 3606: Use of 'RESTORE_PURCHASES_SUCCESS' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.RESTORE_PURCHASES_SUCCESS'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 252, column 60
Warning: 3606: Use of 'RESTORE_PURCHASES_FAILED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.RESTORE_PURCHASES_FAILED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 284, column 63
Warning: 3606: Use of 'PRODUCTS_LOADED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.PRODUCTS_LOADED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 285, column 63
Warning: 3606: Use of 'PRODUCTS_FAILED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.PRODUCTS_FAILED'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 286, column 63
Warning: 3606: Use of 'INVALID_PRODUCT' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.ProductEvent.INVALID_PRODUCT'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 289, column 63
Warning: 3606: Use of 'FINISH_SUCCESS' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.FINISH_SUCCESS'.
D:\Applis\Marees NC ANDROID - 2025 - IA\com\InAppManager.as, line 290, column 63
Warning: 3606: Use of 'FINISH_FAILED' is deprecated. Please use 'com.distriqt.extension.inappbilling.events.PurchaseEvent.FINISH_FAILED'.
I assume I need to replace the old constants (like InAppBillingEvent.PRODUCTS_LOADED) with the fully qualified ones (like ProductEvent.PRODUCTS_LOADED), but I want to make sure I'm doing this correctly and consistently across the code.
Is this the expected change in the latest Distriqt InAppBilling ANE versions?
Thanks for any clarification or best practices!
…________________________________
De : Michael ***@***.***>
Envoyé : jeudi 31 juillet 2025 14:02
À : airsdk/Adobe-Runtime-Support ***@***.***>
Cc : stephanberger4 ***@***.***>; Mention ***@***.***>
Objet : Re: [airsdk/Adobe-Runtime-Support] Google Play Billing v 6.2.1 with SDK 34 (Discussion #3477)
Hi, yes v17.1.0 was released with the play billing update required for android 35
—
Reply to this email directly, view it on GitHub<#3477 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABQWF7UVAQ6PZ3AGFCF2EEL3LGBNHAVCNFSM6AAAAABOOQHED2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJUGEZTAOA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
THANK YOU ! Found it ! It was |
Beta Was this translation helpful? Give feedback.
-
|
Sweet!!! FYI you likely can use https://docs.airnativeextensions.com/docs/application/device-information/unique-device-id if you need to replace that device id ane, or if you shoot it over to me, I can remove the jar and you can see if it works with the shared play services. |
Beta Was this translation helpful? Give feedback.
-
|
That's nice of you ! Here's the ANE if you manaed to remove the jar. If not, I will try to update my code with the link you sent me. |
Beta Was this translation helpful? Give feedback.
-
|
Try this: |
Beta Was this translation helpful? Give feedback.
-
Seems to work !!! THANK YOU |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Do you know if the Play Store requires some time to remove the warning in the developer console? I updated my app with the latest Distriqt ANE, and didn't get any warning related to the IAB version before publishing. However, the new version of the app is now available on the Play Store, and the warning about policy violation is still present in the developer console (in the "Production" tab). Is it normal? Edit: Never mind, it took about 8 hours, but now the warning is gone. |
Beta Was this translation helpful? Give feedback.
-
|
Great to hear! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm using distriqt ANE InAppBilling (https://airnativeextensions.com/extension/com.distriqt.InAppBilling/)
Everything always worked great.
But Google recently requires to us Google Play Billing v6 (I was at v5), AND requires SDK 34 (I was at 33)
If, in my manifest, I'm changing
<meta-data android:name="com.google.android.play.billingclient.version" android:value="5.0.0" />to<meta-data android:name="com.google.android.play.billingclient.version" android:value="6.2.1" />: It's working.But If I'm changing
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="33"/>to
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="34"/>The "buy" button doesn't work anymore in my app. It' s working only if I keep the SDK to 33 (which Google doesn't want anymore).
Is this a known error ? And is it coming from : the ANE ? The AIR SDK ?
Thanks again for your help,
Beta Was this translation helpful? Give feedback.
All reactions