Hi there,

Yes, I do know that SDKBOX is lifeless. However, is there any probability that you’re going to replace it to assist Google Billing Library v4?

Ps. Google is forcing to make use of it ranging from 1.11.2022.

Best,
kds

I too have observed this major problem.

As everyone knows, SDKBOX is lifeless.
Probably no replace is predicted.

Reminder: Starting on August 2, 2022, all new apps should use Billing Library model 4 or newer.
By November 1, 2022, all updates to current apps should use Billing Library model 4 or newer.

And the issue just isn’t simple.
There are vital API modifications between model 4 and model 5, and the strategies accessible in model 4 have been deprecated.
So, in follow, model 5 assist is a should.

Unfortunately, there isn’t any open supply library accessible at the moment that I can hope to search out.

• Able to manage each iOS and Android with a standard interface.
• Support each cocos2d-x 3.x and 4.x
• Compatible with Billing Library model 5

From the place did you discover this? You have completely improper information.
I do have my very own framework written, beforehand it was on model 4 and lately i upgraded to version-5 and that i dont need to do any apis modifications in any respect.

Previously i used to be additionally utilizing sdkbox, however attempt to create your individual wrapper class as soon as and also you dont need to face such points any extra.
I can’t share my code, o/w i would make it easier to.

In conclusion, I believe the one means to do that is to create my very own implementation of in-app billing for Android.
I’ve some expertise with native integration for Android, so I’ve began engaged on it.
If it really works, I wish to share the code.

As for iOS, I’ve no expertise with Objective-C, so it’s an unknown.

Thanks in your replies. Yeah, that is the very best time to spend few days on the wrapper. It might be additionally a superb time to combine different shops (Amazon, Huawei, Samsung and so forth.).

@bluewind00 iOS integration ought to be simpler since you don’t have to make use of any “ndk”. I’ll share the code after I handle to do it (I hate Obj-C too :P). The precedence is Android, sdkbox nonetheless works on iOS.

Hello, I’m dealing with the identical drawback google billing 4 with use sdkbox. Please share supply code to switch sdkbox for android

I’m nonetheless a piece in progress.
I’ll share it when it’s completed, however I can’t promise a deadline.
If you’re in a rush you’ll be able to work on it your self and share it.
Also, I can’t make it totally appropriate with sdkbox::IAP.
I’ll solely implement the options that I take advantage of.

It just isn’t excellent, however I used to be capable of create the performance I wanted.
I wish to share it as a pattern code.

Note that it’s only for Android and never totally appropriate with sdkbox::IAP.
The callback arguments and namespace are totally different.

I don’t assume you should use this code as it’s, however you should use it as a reference to implement the performance you want.

If anybody else has carried out the acquisition performance, please share.

I’m solely conversant in Android at this level.
For iOS, you’ll be able to proceed to make use of sdkbox::IAP, so you’ll be able to establish the platform and use
I’m considering of utilizing my very own code for android and sdkbox::IAP for iOS.

Thanks in your share.
did you check in googleplay? and its work?

Of course, I truly made a check buy on Google Play.
It works high quality.

Hello, it ‘s works for android. Please replace for IOS. i would really like change sdkbox is it not handy now